Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dc7b7ad3d5ea7c47f7cb150793d6cc0eebf255b63cb660f3f0a03424eb0437b

Tx prefix hash: 9adb606b80801f2d4ae686eed10a8cead2e3f33750efeafb65a5a73d20177c2d
Tx public key: 691b1bbb4706f75805ecbbd54e06a01a22e33a1598fcfa5192a2b39e690f3287
Timestamp: 1748202823 Timestamp [UCT]: 2025-05-25 19:53:43 Age [y:d:h:m:s]: 00:193:07:09:27
Block: 1290834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135876 RingCT/type: yes/0
Extra: 01691b1bbb4706f75805ecbbd54e06a01a22e33a1598fcfa5192a2b39e690f32870211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54950e3b0a18b79113692a5763280699eb5a9bf477124405f546ccb81045a36b 0.600000000000 1778305 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": 1290844, "vin": [ { "gen": { "height": 1290834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54950e3b0a18b79113692a5763280699eb5a9bf477124405f546ccb81045a36b" } } ], "extra": [ 1, 105, 27, 27, 187, 71, 6, 247, 88, 5, 236, 187, 213, 78, 6, 160, 26, 34, 227, 58, 21, 152, 252, 250, 81, 146, 162, 179, 158, 105, 15, 50, 135, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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