Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74cad344900d2d3a6f59b422cbd5125b7633b02c22ab0c85645cd5fc9be4b1c3

Tx prefix hash: d42d86dc812a6ccd929c51e48f47052a6aa9dce57a986f62b5229182e9488bc4
Tx public key: e18849de151e81e9075e9ec27c47206f8d50c6f9c25b4f99b248e4f6f2360342
Timestamp: 1721705745 Timestamp [UCT]: 2024-07-23 03:35:45 Age [y:d:h:m:s]: 01:110:04:01:54
Block: 1071684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337253 RingCT/type: yes/0
Extra: 01e18849de151e81e9075e9ec27c47206f8d50c6f9c25b4f99b248e4f6f236034202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 928bcefa60619768576d2f47d8f9ce4646d86cdeb1ca290705c94a1a54f35be6 0.600000000000 1544003 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": 1071694, "vin": [ { "gen": { "height": 1071684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "928bcefa60619768576d2f47d8f9ce4646d86cdeb1ca290705c94a1a54f35be6" } } ], "extra": [ 1, 225, 136, 73, 222, 21, 30, 129, 233, 7, 94, 158, 194, 124, 71, 32, 111, 141, 80, 198, 249, 194, 91, 79, 153, 178, 72, 228, 246, 242, 54, 3, 66, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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