Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 174f3604d43d3d236ccf12a5e620627091992f9a0737631f2b25a9c73d2850fa

Tx prefix hash: 2dacb38860fd9130e0e84effd64c8c0a0df3f18b2e945801bfc9cac5d84f8fdb
Tx public key: d6256b178b0b82f943c71b68d0db5c218f9d2f472d107a242dc66ca376d384e8
Timestamp: 1670171411 Timestamp [UCT]: 2022-12-04 16:30:11 Age [y:d:h:m:s]: 02:084:15:27:38
Block: 645355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582157 RingCT/type: yes/0
Extra: 01d6256b178b0b82f943c71b68d0db5c218f9d2f472d107a242dc66ca376d384e802110000000a33af99f4000000000000000000

1 output(s) for total of 4.463453131000 dcy

stealth address amount amount idx
00: f983a05bd3661bf31e7ea37a2ab2896a171024a2560d2389792225b43a38dd1e 4.463453131000 1085516 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": 645365, "vin": [ { "gen": { "height": 645355 } } ], "vout": [ { "amount": 4463453131, "target": { "key": "f983a05bd3661bf31e7ea37a2ab2896a171024a2560d2389792225b43a38dd1e" } } ], "extra": [ 1, 214, 37, 107, 23, 139, 11, 130, 249, 67, 199, 27, 104, 208, 219, 92, 33, 143, 157, 47, 71, 45, 16, 122, 36, 45, 198, 108, 163, 118, 211, 132, 232, 2, 17, 0, 0, 0, 10, 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