Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19b1ada6087b097ab4aa1869671dcd4b8a6b00d42cece778396f527ecd614894

Tx prefix hash: 7f87b0f99a7033e68c6f6b2ef329decf6207f84f145ad845838f9412acebc5d0
Tx public key: 96881eae2b9363b8e99e875d8df4de2ac370f607d8343972bad5bb25a4e530b7
Timestamp: 1749433567 Timestamp [UCT]: 2025-06-09 01:46:07 Age [y:d:h:m:s]: 00:154:14:22:53
Block: 1301035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108162 RingCT/type: yes/0
Extra: 0196881eae2b9363b8e99e875d8df4de2ac370f607d8343972bad5bb25a4e530b70211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5caca3c4875cb46d9cb42562222c72bcad50ed3631a9aa603845b1057b3367b1 0.600000000000 1788588 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": 1301045, "vin": [ { "gen": { "height": 1301035 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5caca3c4875cb46d9cb42562222c72bcad50ed3631a9aa603845b1057b3367b1" } } ], "extra": [ 1, 150, 136, 30, 174, 43, 147, 99, 184, 233, 158, 135, 93, 141, 244, 222, 42, 195, 112, 246, 7, 216, 52, 57, 114, 186, 213, 187, 37, 164, 229, 48, 183, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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