Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965a0c9edd83e0efb85dd4e35005027b2407200bb22d781e08beb259fba8e0c1

Tx prefix hash: 0a26bc6e8aebab9eedfe9fd120f3dbac3f421fc643356ca27424af6b920f82e0
Tx public key: 654428b80c2b988eeffc59cb524d579f6f85e2ada0cc6e7f549d06676be43377
Timestamp: 1715001638 Timestamp [UCT]: 2024-05-06 13:20:38 Age [y:d:h:m:s]: 00:293:22:36:53
Block: 1016114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210087 RingCT/type: yes/0
Extra: 01654428b80c2b988eeffc59cb524d579f6f85e2ada0cc6e7f549d06676be433770211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaa3186c802e034bbaad3603cf04326ab37860265f3f8f730bf010e5df99bf8d 0.600000000000 1479609 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": 1016124, "vin": [ { "gen": { "height": 1016114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaa3186c802e034bbaad3603cf04326ab37860265f3f8f730bf010e5df99bf8d" } } ], "extra": [ 1, 101, 68, 40, 184, 12, 43, 152, 142, 239, 252, 89, 203, 82, 77, 87, 159, 111, 133, 226, 173, 160, 204, 110, 127, 84, 157, 6, 103, 107, 228, 51, 119, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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