Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fa4bb68969b03dab727fce8ec689b38a0229aa73091de6e01595f309db6b752

Tx prefix hash: 670d19cd0ca2a2b04620d03a3731eac0d03179c217b7733e1493723fe386c2ed
Tx public key: da7e7f0d91628f1ec48bb1d5e7784188d611510d02474e7c8a3e3e79d273b803
Timestamp: 1717128490 Timestamp [UCT]: 2024-05-31 04:08:10 Age [y:d:h:m:s]: 00:357:04:45:36
Block: 1033753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255327 RingCT/type: yes/0
Extra: 01da7e7f0d91628f1ec48bb1d5e7784188d611510d02474e7c8a3e3e79d273b8030211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c896d93b9eeb2862d92dc777f77a0c826a3f7e2729566ac084dd2ad0c6426404 0.600000000000 1502224 of 15

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": 1033763, "vin": [ { "gen": { "height": 1033753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c896d93b9eeb2862d92dc777f77a0c826a3f7e2729566ac084dd2ad0c6426404" } } ], "extra": [ 1, 218, 126, 127, 13, 145, 98, 143, 30, 196, 139, 177, 213, 231, 120, 65, 136, 214, 17, 81, 13, 2, 71, 78, 124, 138, 62, 62, 121, 210, 115, 184, 3, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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