Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf732acb4a888f7e9f86834a4132817d3300e500fa180abbdd229f202c8c13e0

Tx prefix hash: 4008e165c5e8ec4149356bd983cce420796f2acfead82cdbb454d178013e0e5b
Tx public key: a62117bc3eb8c3d3ae66fdbec21f08f6f3b6124b09a02fb539841b1b3c049217
Timestamp: 1724682313 Timestamp [UCT]: 2024-08-26 14:25:13 Age [y:d:h:m:s]: 00:253:08:36:26
Block: 1096370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180959 RingCT/type: yes/0
Extra: 01a62117bc3eb8c3d3ae66fdbec21f08f6f3b6124b09a02fb539841b1b3c04921702110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08acb344a6fc1674bb60e1ccab1e741c4a079cb300c7845dd52c524f246aeb77 0.600000000000 1571559 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": 1096380, "vin": [ { "gen": { "height": 1096370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08acb344a6fc1674bb60e1ccab1e741c4a079cb300c7845dd52c524f246aeb77" } } ], "extra": [ 1, 166, 33, 23, 188, 62, 184, 195, 211, 174, 102, 253, 190, 194, 31, 8, 246, 243, 182, 18, 75, 9, 160, 47, 181, 57, 132, 27, 27, 60, 4, 146, 23, 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