Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 547b8f059c27fb5ddc95594966fae5983a8acd1d1c275f122d2196448c4ad675

Tx prefix hash: a72a9d1345be0243fe40e8b66ec75912445041b6849682911da515fac6b49580
Tx public key: f53f533e0872b4f3c7ed3b2effa534b748ab6dea53139bd62279ef09fa2c2d57
Timestamp: 1724165706 Timestamp [UCT]: 2024-08-20 14:55:06 Age [y:d:h:m:s]: 00:225:23:18:47
Block: 1092097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161359 RingCT/type: yes/0
Extra: 01f53f533e0872b4f3c7ed3b2effa534b748ab6dea53139bd62279ef09fa2c2d5702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1501c392dc60ee26ec7d47ec5cc74d0aa03a6d11d8a6a0ae6921662cfa854a 0.600000000000 1566774 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": 1092107, "vin": [ { "gen": { "height": 1092097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1501c392dc60ee26ec7d47ec5cc74d0aa03a6d11d8a6a0ae6921662cfa854a" } } ], "extra": [ 1, 245, 63, 83, 62, 8, 114, 180, 243, 199, 237, 59, 46, 255, 165, 52, 183, 72, 171, 109, 234, 83, 19, 155, 214, 34, 121, 239, 9, 250, 44, 45, 87, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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