Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 462db956c1568bf3b4a756a7445322b361de290c87e5119654bb05dd261d54c4

Tx prefix hash: e02b92ffa676413941034a38367b6fe2e6a8ccd07a9214efd6d614c9d110c120
Tx public key: 756da553b3d891a80ae9c7d7c670cbf5682aeeecfe3f65d409d42538a46e1f90
Timestamp: 1736507029 Timestamp [UCT]: 2025-01-10 11:03:49 Age [y:d:h:m:s]: 00:163:09:08:15
Block: 1194263 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116386 RingCT/type: yes/0
Extra: 01756da553b3d891a80ae9c7d7c670cbf5682aeeecfe3f65d409d42538a46e1f900211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600110000000 dcy

stealth address amount amount idx
00: 43528dfd8a93eb4154991df9b2318b96b4f1c41e9bf007a751f653b28c15de15 0.600110000000 1680830 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": 1194273, "vin": [ { "gen": { "height": 1194263 } } ], "vout": [ { "amount": 600110000, "target": { "key": "43528dfd8a93eb4154991df9b2318b96b4f1c41e9bf007a751f653b28c15de15" } } ], "extra": [ 1, 117, 109, 165, 83, 179, 216, 145, 168, 10, 233, 199, 215, 198, 112, 203, 245, 104, 42, 238, 236, 254, 63, 101, 212, 9, 212, 37, 56, 164, 110, 31, 144, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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