Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e39ef678a71947644f5b7bb5b0611ab2328419846afb9e051141f5ff19c14288

Tx prefix hash: 7c36f8f94da8f44bb0fd59de41968b003fb4a7b8a0daafc3cf502c81b85f8657
Tx public key: 6b8d11b223e25993bfd78ed64d8332b5b01ac2473586f35f47f8b127edff9dfd
Timestamp: 1719326552 Timestamp [UCT]: 2024-06-25 14:42:32 Age [y:d:h:m:s]: 00:337:18:51:04
Block: 1051963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241438 RingCT/type: yes/0
Extra: 016b8d11b223e25993bfd78ed64d8332b5b01ac2473586f35f47f8b127edff9dfd02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26e9c5798a8152ce1096f57e30ffb1dbef33f26a4aa4ca79b137d0d48fa3044b 0.600000000000 1522284 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": 1051973, "vin": [ { "gen": { "height": 1051963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26e9c5798a8152ce1096f57e30ffb1dbef33f26a4aa4ca79b137d0d48fa3044b" } } ], "extra": [ 1, 107, 141, 17, 178, 35, 226, 89, 147, 191, 215, 142, 214, 77, 131, 50, 181, 176, 26, 194, 71, 53, 134, 243, 95, 71, 248, 177, 39, 237, 255, 157, 253, 2, 17, 0, 0, 0, 3, 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