Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e8a6a96af4f1c86b06726a1d50daf23ae239a547c7723871a71f1d347b9731a

Tx prefix hash: 3b0dae799cc71a73f690a67f231ed0c61e73044e87786b2e95910b8e943dc448
Tx public key: db3b85295d8a717b40c3151197bd50352f401805f0627b7cb09c05c9256588bd
Timestamp: 1712805104 Timestamp [UCT]: 2024-04-11 03:11:44 Age [y:d:h:m:s]: 01:208:03:32:25
Block: 997879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407442 RingCT/type: yes/0
Extra: 01db3b85295d8a717b40c3151197bd50352f401805f0627b7cb09c05c9256588bd02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe9e249993930ca1e05e9ee124aee9e2d253da456d700686756cd2362eb37e16 0.600000000000 1458313 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": 997889, "vin": [ { "gen": { "height": 997879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe9e249993930ca1e05e9ee124aee9e2d253da456d700686756cd2362eb37e16" } } ], "extra": [ 1, 219, 59, 133, 41, 93, 138, 113, 123, 64, 195, 21, 17, 151, 189, 80, 53, 47, 64, 24, 5, 240, 98, 123, 124, 176, 156, 5, 201, 37, 101, 136, 189, 2, 17, 0, 0, 0, 4, 82, 212, 126, 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