Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff416b274518694b4a855eff24a4fc4523e38c885b09bdd24cbaebd9c4664f59

Tx prefix hash: ce3fb5a2d2c4caeb4873da7d44043c14535049233b48cb9a0fbd0c4d7c2df64e
Tx public key: 47a8c8a72a93356617bfcde77ab4a07966e97e150151246fb950a710df015b6d
Timestamp: 1732214724 Timestamp [UCT]: 2024-11-21 18:45:24 Age [y:d:h:m:s]: 00:002:10:56:12
Block: 1158720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1762 RingCT/type: yes/0
Extra: 0147a8c8a72a93356617bfcde77ab4a07966e97e150151246fb950a710df015b6d0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cffa9c9e37390515d607d8440612c184624e2d9e868956b5cb3049d257b63326 0.600000000000 1644349 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": 1158730, "vin": [ { "gen": { "height": 1158720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cffa9c9e37390515d607d8440612c184624e2d9e868956b5cb3049d257b63326" } } ], "extra": [ 1, 71, 168, 200, 167, 42, 147, 53, 102, 23, 191, 205, 231, 122, 180, 160, 121, 102, 233, 126, 21, 1, 81, 36, 111, 185, 80, 167, 16, 223, 1, 91, 109, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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