Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f273bb9c426433d72b06e0bb3d25e32d5052ad9922a751600dffcb4f19630e53

Tx prefix hash: c08964651b7c60289a3c1423e8af01b5c6d9f98760fabacbf315d8463de71854
Tx public key: f0737a145e6ac1141e34c3df7c80e5d33bd4b401202f708d64f381f9c2f4d2ca
Timestamp: 1719607632 Timestamp [UCT]: 2024-06-28 20:47:12 Age [y:d:h:m:s]: 01:142:20:44:27
Block: 1054289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360672 RingCT/type: yes/0
Extra: 01f0737a145e6ac1141e34c3df7c80e5d33bd4b401202f708d64f381f9c2f4d2ca0211000000020cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51c77ef3b3b02fac3e46aead1538c2a1b3f23d24990916777bd31026bb79e5df 0.600000000000 1524650 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": 1054299, "vin": [ { "gen": { "height": 1054289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51c77ef3b3b02fac3e46aead1538c2a1b3f23d24990916777bd31026bb79e5df" } } ], "extra": [ 1, 240, 115, 122, 20, 94, 106, 193, 20, 30, 52, 195, 223, 124, 128, 229, 211, 59, 212, 180, 1, 32, 47, 112, 141, 100, 243, 129, 249, 194, 244, 210, 202, 2, 17, 0, 0, 0, 2, 12, 206, 6, 54, 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