Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1b11758a51b78267dabe27928c0f6d73331158e1409842289b09f37a05aa39

Tx prefix hash: 27fbc4aae96764c3dae2ae7f7eec3a449f40402b138f624ad1d343bd980d6c82
Tx public key: 34d1cbdfbf4d055a726d4a134312f184310f25ee1ffc70e5de3aeb87a6e1634f
Timestamp: 1732278341 Timestamp [UCT]: 2024-11-22 12:25:41 Age [y:d:h:m:s]: 00:002:01:40:33
Block: 1159251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1487 RingCT/type: yes/0
Extra: 0134d1cbdfbf4d055a726d4a134312f184310f25ee1ffc70e5de3aeb87a6e1634f021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53e155ab14223bb02d929b529d7f63d3355457f60345e04c57044a3ad1e85ff6 0.600000000000 1644884 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": 1159261, "vin": [ { "gen": { "height": 1159251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53e155ab14223bb02d929b529d7f63d3355457f60345e04c57044a3ad1e85ff6" } } ], "extra": [ 1, 52, 209, 203, 223, 191, 77, 5, 90, 114, 109, 74, 19, 67, 18, 241, 132, 49, 15, 37, 238, 31, 252, 112, 229, 222, 58, 235, 135, 166, 225, 99, 79, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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