Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c31f7236159010fef85144315e101378253dd00a7a4d1ed45ac5d9f53e88ad8

Tx prefix hash: 35daf47e15ec9e7bc7b65886acc7fcd9ffb03f9b2688b7cfd2953c24e520bbc5
Tx public key: 4c1b75f036b325fb1a9628f838e96db18ebdfee3e687974f5bf4c7f284322dba
Timestamp: 1754515680 Timestamp [UCT]: 2025-08-06 21:28:00 Age [y:d:h:m:s]: 00:155:07:56:58
Block: 1341714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110121 RingCT/type: yes/0
Extra: 014c1b75f036b325fb1a9628f838e96db18ebdfee3e687974f5bf4c7f284322dba02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07742cb8ca8518a2292d512770720cd60465ad70d302679a3a2f9c9b7d071072 0.600000000000 1829541 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": 1341724, "vin": [ { "gen": { "height": 1341714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07742cb8ca8518a2292d512770720cd60465ad70d302679a3a2f9c9b7d071072" } } ], "extra": [ 1, 76, 27, 117, 240, 54, 179, 37, 251, 26, 150, 40, 248, 56, 233, 109, 177, 142, 189, 254, 227, 230, 135, 151, 79, 91, 244, 199, 242, 132, 50, 45, 186, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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