Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cd8aec776e8a4ecce21cd2d617756c4f59d684f9ff16730ebf6c5876c3a8ac3

Tx prefix hash: f9cd1369ef552af78e11add90b1676763ba882723d0b5d36c6b2261503a9a486
Tx public key: 268a87a0564560a76a77507cf4fc81aafb43396ac3d699e9dacca3ecc0074d5a
Timestamp: 1727187368 Timestamp [UCT]: 2024-09-24 14:16:08 Age [y:d:h:m:s]: 00:109:20:21:53
Block: 1117146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78544 RingCT/type: yes/0
Extra: 01268a87a0564560a76a77507cf4fc81aafb43396ac3d699e9dacca3ecc0074d5a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bf3f9e10c0814b2d4f8e6e7794907c10ec66e0643850ad4d49d1be7f70cfc6a 0.600000000000 1597877 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": 1117156, "vin": [ { "gen": { "height": 1117146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bf3f9e10c0814b2d4f8e6e7794907c10ec66e0643850ad4d49d1be7f70cfc6a" } } ], "extra": [ 1, 38, 138, 135, 160, 86, 69, 96, 167, 106, 119, 80, 124, 244, 252, 129, 170, 251, 67, 57, 106, 195, 214, 153, 233, 218, 204, 163, 236, 192, 7, 77, 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