Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5ad35c0788caa66d1b8c45c495ec321f98cb3f98a12d615665ef597513c0a9c

Tx prefix hash: 7b1015ec042a9239f4aed0c384e6d793806ce436174ac243475c9fd8677cc3e3
Tx public key: e136ad559e89fabb9ab55c5e91632bd3fb9f9b7c78f8d67f11436125e3895e46
Timestamp: 1732954504 Timestamp [UCT]: 2024-11-30 08:15:04 Age [y:d:h:m:s]: 00:026:05:41:26
Block: 1164858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18795 RingCT/type: yes/0
Extra: 01e136ad559e89fabb9ab55c5e91632bd3fb9f9b7c78f8d67f11436125e3895e46021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b386290825d9cb4c020da804a0c9101a161372cda6b22624f890ca8d7e8dff9 0.600000000000 1650533 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": 1164868, "vin": [ { "gen": { "height": 1164858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b386290825d9cb4c020da804a0c9101a161372cda6b22624f890ca8d7e8dff9" } } ], "extra": [ 1, 225, 54, 173, 85, 158, 137, 250, 187, 154, 181, 92, 94, 145, 99, 43, 211, 251, 159, 155, 124, 120, 248, 214, 127, 17, 67, 97, 37, 227, 137, 94, 70, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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