Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1f6620278bb9c3fbcb3d9d226ee0fc9033d3481b9798a200edd23df3ad64ef0

Tx prefix hash: 00849f4a904b8ac2fdd2b62b7cea6fe35dc52551954904214673c3402ff02a0f
Tx public key: 5d016a41199087856d0ffcda862b03ea1e3a3c9cd8edee51d53559e1f28348a7
Timestamp: 1743600523 Timestamp [UCT]: 2025-04-02 13:28:43 Age [y:d:h:m:s]: 00:280:00:29:22
Block: 1252728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197930 RingCT/type: yes/0
Extra: 015d016a41199087856d0ffcda862b03ea1e3a3c9cd8edee51d53559e1f28348a7021100000006a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b92a25c60a8f0dec63e66e8ef56d1715d9a7a7df8a45343436b9cd9a1038f9f3 0.600000000000 1739809 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": 1252738, "vin": [ { "gen": { "height": 1252728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b92a25c60a8f0dec63e66e8ef56d1715d9a7a7df8a45343436b9cd9a1038f9f3" } } ], "extra": [ 1, 93, 1, 106, 65, 25, 144, 135, 133, 109, 15, 252, 218, 134, 43, 3, 234, 30, 58, 60, 156, 216, 237, 238, 81, 213, 53, 89, 225, 242, 131, 72, 167, 2, 17, 0, 0, 0, 6, 162, 237, 1, 107, 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