Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f3147fd3080bef622b1e9a963a630dab205eeb1d151bf65a7139c0d67f02afbe

Tx prefix hash: a9b6a3efe1a1abf1d705dac8c386e261c2f308390ff121038c0d3ebddeaf1970
Tx public key: 495e607184acec4fff5ce9b6e68b261f29d3ad34b66bc765a87b143c4379c855
Timestamp: 1650723240 Timestamp [UCT]: 2022-04-23 14:14:00 Age [y:d:h:m:s]: 02:248:23:30:40
Block: 486440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 697891 RingCT/type: yes/0
Extra: 01495e607184acec4fff5ce9b6e68b261f29d3ad34b66bc765a87b143c4379c855021100000001bf7ee4e7000000000000000000

1 output(s) for total of 15.004536162000 dcy

stealth address amount amount idx
00: 35e8ddad2e3ad16724e677b4f25ffdee82184a1a4556931528d309afa4924622 15.004536162000 908723 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 486450, "vin": [ { "gen": { "height": 486440 } } ], "vout": [ { "amount": 15004536162, "target": { "key": "35e8ddad2e3ad16724e677b4f25ffdee82184a1a4556931528d309afa4924622" } } ], "extra": [ 1, 73, 94, 96, 113, 132, 172, 236, 79, 255, 92, 233, 182, 230, 139, 38, 31, 41, 211, 173, 52, 182, 107, 199, 101, 168, 123, 20, 60, 67, 121, 200, 85, 2, 17, 0, 0, 0, 1, 191, 126, 228, 231, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8