Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16c12853c0053e9fc0906326fdd7c7f4b58e402d01c5ba3e7ec72790a2a6e39a

Tx prefix hash: d6e74251d016aeab94f87e3c77ecc5cfc4e6b1988026cf20171f1a39509235d4
Tx public key: 1e00c12484f9b59ead0d703674556c38e185cb5316c9bd875c6c86503c29fcc8
Timestamp: 1713865864 Timestamp [UCT]: 2024-04-23 09:51:04 Age [y:d:h:m:s]: 00:358:09:52:16
Block: 1006704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256217 RingCT/type: yes/0
Extra: 011e00c12484f9b59ead0d703674556c38e185cb5316c9bd875c6c86503c29fcc80211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57fe50f48c3310037a7070c32bb3f392ae3241f853a4b96bbf901313d8a3d363 0.600000000000 1467814 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": 1006714, "vin": [ { "gen": { "height": 1006704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57fe50f48c3310037a7070c32bb3f392ae3241f853a4b96bbf901313d8a3d363" } } ], "extra": [ 1, 30, 0, 193, 36, 132, 249, 181, 158, 173, 13, 112, 54, 116, 85, 108, 56, 225, 133, 203, 83, 22, 201, 189, 135, 92, 108, 134, 80, 60, 41, 252, 200, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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