Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9eaf959b389145bf8c3d435b3874b349c2d46bd24232cf15f2d0a2d6ce2a91d5

Tx prefix hash: 3af0bf9472ed17e50120cce18e62be8a3a9ca5de84af31bb4090a673e75cdc47
Tx public key: 62e7c926f5aa653b1a26bbe553fe5fd67b49fe6e98924a5a43524593374e753c
Timestamp: 1700787615 Timestamp [UCT]: 2023-11-24 01:00:15 Age [y:d:h:m:s]: 01:056:17:38:52
Block: 898270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301914 RingCT/type: yes/0
Extra: 0162e7c926f5aa653b1a26bbe553fe5fd67b49fe6e98924a5a43524593374e753c0211000000014b8f5122000000000000000000

1 output(s) for total of 0.648124720000 dcy

stealth address amount amount idx
00: 9765c95d6552de94e876cdf6850b58caccce3bceb831df2f8bd4b749f6c51ba1 0.648124720000 1354683 of 0

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": 898280, "vin": [ { "gen": { "height": 898270 } } ], "vout": [ { "amount": 648124720, "target": { "key": "9765c95d6552de94e876cdf6850b58caccce3bceb831df2f8bd4b749f6c51ba1" } } ], "extra": [ 1, 98, 231, 201, 38, 245, 170, 101, 59, 26, 38, 187, 229, 83, 254, 95, 214, 123, 73, 254, 110, 152, 146, 74, 90, 67, 82, 69, 147, 55, 78, 117, 60, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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