Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b1aa8565cac209fb7282437332ed5375e3da14326bde4dc4350c15ed6ae8067

Tx prefix hash: a0b0229675dfec470dd502c3b556453337380b2861d38b53ac0b690a1dcc3dc2
Tx public key: 8d50ec4948d33d1b2a5e114a782e3b907b74027e01a444f528581aa709593d05
Timestamp: 1755264539 Timestamp [UCT]: 2025-08-15 13:28:59 Age [y:d:h:m:s]: 00:096:12:22:14
Block: 1347239 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68686 RingCT/type: yes/0
Extra: 018d50ec4948d33d1b2a5e114a782e3b907b74027e01a444f528581aa709593d05021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f04be62c6d5d1e4c77e52ceba594871e13ad31905d217f5a825c089ce5973d23 0.600000000000 1835154 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": 1347249, "vin": [ { "gen": { "height": 1347239 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f04be62c6d5d1e4c77e52ceba594871e13ad31905d217f5a825c089ce5973d23" } } ], "extra": [ 1, 141, 80, 236, 73, 72, 211, 61, 27, 42, 94, 17, 74, 120, 46, 59, 144, 123, 116, 2, 126, 1, 164, 68, 245, 40, 88, 26, 167, 9, 89, 61, 5, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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