Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e5867272927f040eb6261d7a99fee40884d13b8308ebb4c39d9a6125720ca5

Tx prefix hash: 530f58df3b1f0e96cb078b3e62e9d52f2cb64e59ce802ec41c79fd58ca76c50c
Tx public key: a7cce0378b9725cae1a064e284a1afbc17b9c1de6a1c506122266a13a7964023
Timestamp: 1702929568 Timestamp [UCT]: 2023-12-18 19:59:28 Age [y:d:h:m:s]: 01:325:13:55:43
Block: 916032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 491542 RingCT/type: yes/0
Extra: 01a7cce0378b9725cae1a064e284a1afbc17b9c1de6a1c506122266a13a796402302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 378212edd4b64c034ce98855a520a2852fa8aa0ced4dd8514986e5c480af25d1 0.600000000000 1373490 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": 916042, "vin": [ { "gen": { "height": 916032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "378212edd4b64c034ce98855a520a2852fa8aa0ced4dd8514986e5c480af25d1" } } ], "extra": [ 1, 167, 204, 224, 55, 139, 151, 37, 202, 225, 160, 100, 226, 132, 161, 175, 188, 23, 185, 193, 222, 106, 28, 80, 97, 34, 38, 106, 19, 167, 150, 64, 35, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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