Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5eef6174da700dcc4b0371fcaf242c1950fc9f8bf5bd06da07ad60c4e1fa8ce

Tx prefix hash: 2dda8bdcfa4a3b7bbadbca87a01715a66541bbef2f47a861ee1c49e7b286eaa4
Tx public key: e3e7567360c36038c1589e2f267eeb21bc0b2aef78ac3b91d61f28a3e2af9ac0
Timestamp: 1751009181 Timestamp [UCT]: 2025-06-27 07:26:21 Age [y:d:h:m:s]: 00:144:00:41:30
Block: 1313717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100957 RingCT/type: yes/0
Extra: 01e3e7567360c36038c1589e2f267eeb21bc0b2aef78ac3b91d61f28a3e2af9ac00211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f7dbf1c5207d6880e95fafc241e513bac240b76a160f2db57730d32bfde0893 0.600000000000 1801360 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": 1313727, "vin": [ { "gen": { "height": 1313717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f7dbf1c5207d6880e95fafc241e513bac240b76a160f2db57730d32bfde0893" } } ], "extra": [ 1, 227, 231, 86, 115, 96, 195, 96, 56, 193, 88, 158, 47, 38, 126, 235, 33, 188, 11, 42, 239, 120, 172, 59, 145, 214, 31, 40, 163, 226, 175, 154, 192, 2, 17, 0, 0, 0, 1, 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