Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 684d0b3618c827f126968ffc93f4094e880f8a3ea8e6680bcd64984ce3c0b176

Tx prefix hash: a1ab31f91dfc1a29855b2a0a5832d4f6cfa8202178db68f99726786400c1bb04
Tx public key: 3111076ba3f562bf77e6088aefa93ff8e6413c3be147634d6e313e883b59ba69
Timestamp: 1695593326 Timestamp [UCT]: 2023-09-24 22:08:46 Age [y:d:h:m:s]: 01:153:00:43:05
Block: 855413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370397 RingCT/type: yes/0
Extra: 013111076ba3f562bf77e6088aefa93ff8e6413c3be147634d6e313e883b59ba690211000000084b8f5122000000000000000000

1 output(s) for total of 0.898797138000 dcy

stealth address amount amount idx
00: 2b75e1cc46dc25efc194cf4978a6bc7344c3d68b468ebb4c0b4eb35a29d362a7 0.898797138000 1309433 of 0

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": 855423, "vin": [ { "gen": { "height": 855413 } } ], "vout": [ { "amount": 898797138, "target": { "key": "2b75e1cc46dc25efc194cf4978a6bc7344c3d68b468ebb4c0b4eb35a29d362a7" } } ], "extra": [ 1, 49, 17, 7, 107, 163, 245, 98, 191, 119, 230, 8, 138, 239, 169, 63, 248, 230, 65, 60, 59, 225, 71, 99, 77, 110, 49, 62, 136, 59, 89, 186, 105, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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