Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6f8cec3415b126cd73f83a71438fe5724a9ae51f48d456043dbf914acc93bb9

Tx prefix hash: f6dee1b912b6427caaaa3eecfda69a3070174c6ce6b8180dc816366b66bb34ba
Tx public key: 8bca32e42777f1898e9cd8de9a13e9cb35881faf7e45a927a73a25430f61ac0e
Timestamp: 1715735993 Timestamp [UCT]: 2024-05-15 01:19:53 Age [y:d:h:m:s]: 01:009:01:23:15
Block: 1022206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267408 RingCT/type: yes/0
Extra: 018bca32e42777f1898e9cd8de9a13e9cb35881faf7e45a927a73a25430f61ac0e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d91e4dbd93dca12cd0dcc5968f64f160b2c6e6883cf49327a371ff45bd5562f 0.600000000000 1486739 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": 1022216, "vin": [ { "gen": { "height": 1022206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d91e4dbd93dca12cd0dcc5968f64f160b2c6e6883cf49327a371ff45bd5562f" } } ], "extra": [ 1, 139, 202, 50, 228, 39, 119, 241, 137, 142, 156, 216, 222, 154, 19, 233, 203, 53, 136, 31, 175, 126, 69, 169, 39, 167, 58, 37, 67, 15, 97, 172, 14, 2, 17, 0, 0, 0, 1, 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