Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98969ede9c56726da0ba3c2f6425c2da44bbfeb546a33aa13b9ec72b4c9a9a7a

Tx prefix hash: 546603bc00ec47d5e56819e249bbf05808c32885e3f287b1a2adf406e0d23b62
Tx public key: e67da300200e1ccd1e792e9523897718c0aa7d62b379c46487956b39e8cf7d2c
Timestamp: 1708320314 Timestamp [UCT]: 2024-02-19 05:25:14 Age [y:d:h:m:s]: 01:263:05:22:31
Block: 960722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446872 RingCT/type: yes/0
Extra: 01e67da300200e1ccd1e792e9523897718c0aa7d62b379c46487956b39e8cf7d2c0211000000016179ba94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51e3fa97e6bd87f42c66350135a8a31ee7598b1740d5053c0c98c0d0c475856e 0.600000000000 1420309 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": 960732, "vin": [ { "gen": { "height": 960722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51e3fa97e6bd87f42c66350135a8a31ee7598b1740d5053c0c98c0d0c475856e" } } ], "extra": [ 1, 230, 125, 163, 0, 32, 14, 28, 205, 30, 121, 46, 149, 35, 137, 119, 24, 192, 170, 125, 98, 179, 121, 196, 100, 135, 149, 107, 57, 232, 207, 125, 44, 2, 17, 0, 0, 0, 1, 97, 121, 186, 148, 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