Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57f6b7fb02c2f5033237fe6e83219ef5fdfb531e9a88f38795c8ff2603ba57ed

Tx prefix hash: 09edaa7dbfd918a833e4aff88be71e3baae50fb96642f5f06471ca65910ca9e5
Tx public key: 3fe847f41a01f8721994cc49af3ba3841833fd1972c3962dc4dc9a8eb0accb58
Timestamp: 1750180140 Timestamp [UCT]: 2025-06-17 17:09:00 Age [y:d:h:m:s]: 00:153:04:56:25
Block: 1307084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107290 RingCT/type: yes/0
Extra: 013fe847f41a01f8721994cc49af3ba3841833fd1972c3962dc4dc9a8eb0accb580211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c73c6ffacba2bfb36d92971a46d6f462c685970fad10d4aea97f469709d026a3 0.600000000000 1794693 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": 1307094, "vin": [ { "gen": { "height": 1307084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c73c6ffacba2bfb36d92971a46d6f462c685970fad10d4aea97f469709d026a3" } } ], "extra": [ 1, 63, 232, 71, 244, 26, 1, 248, 114, 25, 148, 204, 73, 175, 59, 163, 132, 24, 51, 253, 25, 114, 195, 150, 45, 196, 220, 154, 142, 176, 172, 203, 88, 2, 17, 0, 0, 0, 2, 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