Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf239cd71c67f6fc06693fecc40e34cb74750d2da37873878cd33f9c9d9777a0

Tx prefix hash: 156f1e2fed210310eff7c0e130ed947f18c4523f462df915c56be92a3f1fcbfe
Tx public key: 6e784ca92ca64f24a47d283c147b5b84354eb53cb801a8081aceb7017f287baf
Timestamp: 1706209536 Timestamp [UCT]: 2024-01-25 19:05:36 Age [y:d:h:m:s]: 01:035:07:41:48
Block: 943192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286309 RingCT/type: yes/0
Extra: 016e784ca92ca64f24a47d283c147b5b84354eb53cb801a8081aceb7017f287baf02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6f8ccf6862e089efa2f068c18a23513ff0b316ea2b174c2c59dea28ac4d6a79 0.600000000000 1401392 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": 943202, "vin": [ { "gen": { "height": 943192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6f8ccf6862e089efa2f068c18a23513ff0b316ea2b174c2c59dea28ac4d6a79" } } ], "extra": [ 1, 110, 120, 76, 169, 44, 166, 79, 36, 164, 125, 40, 60, 20, 123, 91, 132, 53, 78, 181, 60, 184, 1, 168, 8, 26, 206, 183, 1, 127, 40, 123, 175, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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