Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63eeb20c34b31cd665693dc02f7a2094afbbcb5c81e5f9198876fc65e3352938

Tx prefix hash: abf55c4e68a1f10c446a92387872dba71bbe5077e4eb5c2701a23669de8e11cc
Tx public key: 472de5775ddcb68b46c67325d81811a3d4f9be7a65d17d8f61c35abd1329f0c5
Timestamp: 1728929687 Timestamp [UCT]: 2024-10-14 18:14:47 Age [y:d:h:m:s]: 00:041:01:02:38
Block: 1131587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29302 RingCT/type: yes/0
Extra: 01472de5775ddcb68b46c67325d81811a3d4f9be7a65d17d8f61c35abd1329f0c502110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f840a2345d560768382728f8cb560cee7fd84c877c203b86b5eb6554707194c1 0.600000000000 1614490 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": 1131597, "vin": [ { "gen": { "height": 1131587 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f840a2345d560768382728f8cb560cee7fd84c877c203b86b5eb6554707194c1" } } ], "extra": [ 1, 71, 45, 229, 119, 93, 220, 182, 139, 70, 198, 115, 37, 216, 24, 17, 163, 212, 249, 190, 122, 101, 209, 125, 143, 97, 195, 90, 189, 19, 41, 240, 197, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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