Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 675f199b0c48fc3be3602ee034b2fe5cfaeffbe5c78783616ed1572d6a7992aa

Tx prefix hash: 8105623c10c101c00248c06120b0edfecbd4106cb9fab91a88bab8c86e8b5732
Tx public key: 253f65a40e4f9e9089cbe21cf77a5c1428893d920ec18b09dd8e5d975dced161
Timestamp: 1738088293 Timestamp [UCT]: 2025-01-28 18:18:13 Age [y:d:h:m:s]: 00:322:03:14:13
Block: 1207107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228012 RingCT/type: yes/0
Extra: 01253f65a40e4f9e9089cbe21cf77a5c1428893d920ec18b09dd8e5d975dced161021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d4e5ef93e1a49886b847ebe28c7b33c0061f1a2ee3d8ffe1f0d62882d4a4fe9 0.600000000000 1693828 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": 1207117, "vin": [ { "gen": { "height": 1207107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d4e5ef93e1a49886b847ebe28c7b33c0061f1a2ee3d8ffe1f0d62882d4a4fe9" } } ], "extra": [ 1, 37, 63, 101, 164, 14, 79, 158, 144, 137, 203, 226, 28, 247, 122, 92, 20, 40, 137, 61, 146, 14, 193, 139, 9, 221, 142, 93, 151, 93, 206, 209, 97, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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