Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb60974f69700387d9d22dd7e1532ce6d21d6b600c49ec2b9383f70cc3ea6d8

Tx prefix hash: 25372e18417e230ce1bd17e04a0ec1567b17244fc6f684e0cfa3aedd952af263
Tx public key: 1e05d4ab7768f2034a6907013662ac83ee43c7d318a39327a9596e34453e8f26
Timestamp: 1682591492 Timestamp [UCT]: 2023-04-27 10:31:32 Age [y:d:h:m:s]: 02:002:20:43:28
Block: 747670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 524189 RingCT/type: yes/0
Extra: 011e05d4ab7768f2034a6907013662ac83ee43c7d318a39327a9596e34453e8f2602110000000933af99f4000000000000000000

1 output(s) for total of 2.044839021000 dcy

stealth address amount amount idx
00: 3c927149807846add7141761bb2f5e7b30d0eaa6c30b2095be03c8a70b7dac8a 2.044839021000 1195397 of 0

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": 747680, "vin": [ { "gen": { "height": 747670 } } ], "vout": [ { "amount": 2044839021, "target": { "key": "3c927149807846add7141761bb2f5e7b30d0eaa6c30b2095be03c8a70b7dac8a" } } ], "extra": [ 1, 30, 5, 212, 171, 119, 104, 242, 3, 74, 105, 7, 1, 54, 98, 172, 131, 238, 67, 199, 211, 24, 163, 147, 39, 169, 89, 110, 52, 69, 62, 143, 38, 2, 17, 0, 0, 0, 9, 51, 175, 153, 244, 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