Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce04243b4f46b5edde00d4ea35ac93841a9c5e9f203dc84fd4a4193950138f20

Tx prefix hash: 66a348a616247b607da66dbd3f42794316b44e604330ba675201459ba9de2a16
Tx public key: cccf5cba83621afbe092fb93efd3e1541d625a69b3a2916ec0e0bfa8dca0fc54
Timestamp: 1703032921 Timestamp [UCT]: 2023-12-20 00:42:01 Age [y:d:h:m:s]: 01:107:07:25:43
Block: 916894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337819 RingCT/type: yes/0
Extra: 01cccf5cba83621afbe092fb93efd3e1541d625a69b3a2916ec0e0bfa8dca0fc5402110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5ce70733fe99542e2a05896f2e344a5c207a1bc0a5d97c95881868a8d31ec44 0.600000000000 1374456 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": 916904, "vin": [ { "gen": { "height": 916894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5ce70733fe99542e2a05896f2e344a5c207a1bc0a5d97c95881868a8d31ec44" } } ], "extra": [ 1, 204, 207, 92, 186, 131, 98, 26, 251, 224, 146, 251, 147, 239, 211, 225, 84, 29, 98, 90, 105, 179, 162, 145, 110, 192, 224, 191, 168, 220, 160, 252, 84, 2, 17, 0, 0, 0, 5, 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