Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd17ecf72bde69961e76796bd06dc3f8c059e87eabbc505b0ebe0d67f1b69d33

Tx prefix hash: f803955904072254a1d502f47c2231665c32bfe3ac9e87503d30ce743eed71e3
Tx public key: 7a01111ca6b2e9140aa07e7a959bc54a2d1be35c6d2cf7e0e169304ffbef93ce
Timestamp: 1715526967 Timestamp [UCT]: 2024-05-12 15:16:07 Age [y:d:h:m:s]: 00:275:21:39:54
Block: 1020506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197164 RingCT/type: yes/0
Extra: 017a01111ca6b2e9140aa07e7a959bc54a2d1be35c6d2cf7e0e169304ffbef93ce021100000006679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4bd002d296249497cf46432aabacfda4371fb57f7b578f756562c80167ea7da 0.600000000000 1484583 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": 1020516, "vin": [ { "gen": { "height": 1020506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4bd002d296249497cf46432aabacfda4371fb57f7b578f756562c80167ea7da" } } ], "extra": [ 1, 122, 1, 17, 28, 166, 178, 233, 20, 10, 160, 126, 122, 149, 155, 197, 74, 45, 27, 227, 92, 109, 44, 247, 224, 225, 105, 48, 79, 251, 239, 147, 206, 2, 17, 0, 0, 0, 6, 103, 154, 138, 129, 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