Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6516cdc61c703c1606cb759cc5fabce02a3264e7ded1f6beb0aaf2784bc69860

Tx prefix hash: 244c687c0a7c526fd0c06ee9dcb290b206de5cfb2c8868a9f23ecce3d23f6184
Tx public key: 30217022db6c6bfd8a12ccff685dacd12a5bc15c85b65b8521493cac200dc75a
Timestamp: 1727793141 Timestamp [UCT]: 2024-10-01 14:32:21 Age [y:d:h:m:s]: 00:165:07:38:53
Block: 1122168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117969 RingCT/type: yes/0
Extra: 0130217022db6c6bfd8a12ccff685dacd12a5bc15c85b65b8521493cac200dc75a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f914f469dfa7df739a89c25970d04a7f45a3206794dfb2a93cbb7d3c1bf9b73 0.600000000000 1604567 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": 1122178, "vin": [ { "gen": { "height": 1122168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f914f469dfa7df739a89c25970d04a7f45a3206794dfb2a93cbb7d3c1bf9b73" } } ], "extra": [ 1, 48, 33, 112, 34, 219, 108, 107, 253, 138, 18, 204, 255, 104, 93, 172, 209, 42, 91, 193, 92, 133, 182, 91, 133, 33, 73, 60, 172, 32, 13, 199, 90, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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