Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d4d0085f9876831efb0d14db37cb10ff910c02b544bb26f8e41a2db89cf75e1

Tx prefix hash: bd2e459dabcc3cb71c1011f67024bf761af93dde06ac6fbe9a5cfcbd79051c9d
Tx public key: b06e93210c816bf6bd516849d51b60246b9d9c31a67985a3a9cd64a6b2e355e1
Timestamp: 1748271883 Timestamp [UCT]: 2025-05-26 15:04:43 Age [y:d:h:m:s]: 00:223:10:27:42
Block: 1291407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157449 RingCT/type: yes/0
Extra: 01b06e93210c816bf6bd516849d51b60246b9d9c31a67985a3a9cd64a6b2e355e10211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f479239a08431756e68f1264d4f47368b28f19f1d7241a1b35176df39c548b7e 0.600000000000 1778878 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": 1291417, "vin": [ { "gen": { "height": 1291407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f479239a08431756e68f1264d4f47368b28f19f1d7241a1b35176df39c548b7e" } } ], "extra": [ 1, 176, 110, 147, 33, 12, 129, 107, 246, 189, 81, 104, 73, 213, 27, 96, 36, 107, 157, 156, 49, 166, 121, 133, 163, 169, 205, 100, 166, 178, 227, 85, 225, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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