Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e647012927aaab30b4ab1cebb09346ce1fb6c211436d0d6fdedc8d12165fe9e0

Tx prefix hash: 347afd5ec247300739ea48d22cd672bc66f794ac05e41b31084c2ddec5d356be
Tx public key: c86e5bf22de7a7f0e07a5be915dd7fb725ea63b060c46f38b4ae219cf2fc93d7
Timestamp: 1737630533 Timestamp [UCT]: 2025-01-23 11:08:53 Age [y:d:h:m:s]: 00:146:20:51:12
Block: 1203526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104687 RingCT/type: yes/0
Extra: 01c86e5bf22de7a7f0e07a5be915dd7fb725ea63b060c46f38b4ae219cf2fc93d70211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5829700158ffc902ad4b3ab784ebf741d5801dbbc3d0cc14f68ea0e0b4184f1b 0.600000000000 1690203 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": 1203536, "vin": [ { "gen": { "height": 1203526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5829700158ffc902ad4b3ab784ebf741d5801dbbc3d0cc14f68ea0e0b4184f1b" } } ], "extra": [ 1, 200, 110, 91, 242, 45, 231, 167, 240, 224, 122, 91, 233, 21, 221, 127, 183, 37, 234, 99, 176, 96, 196, 111, 56, 180, 174, 33, 156, 242, 252, 147, 215, 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