Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80f0b4015d116aa6064c8c1677014880f48c5ba06ee9e8a650c9e59648f8e643

Tx prefix hash: b3030ae26d2ed3d0ae6f88e1734d1dfada4a0fff9802a074cddecbce56fe592a
Tx public key: 4b78f0a3b012a70e022058560e7be54a5373d0862dd69f34d674d2eecaa59655
Timestamp: 1721649984 Timestamp [UCT]: 2024-07-22 12:06:24 Age [y:d:h:m:s]: 00:095:07:25:23
Block: 1071234 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68231 RingCT/type: yes/0
Extra: 014b78f0a3b012a70e022058560e7be54a5373d0862dd69f34d674d2eecaa5965502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34e86e63cf20d5eca245ab03072e20ace625bf1bb9cd6ab422d72fb04f93c6fb 0.600000000000 1543379 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": 1071244, "vin": [ { "gen": { "height": 1071234 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34e86e63cf20d5eca245ab03072e20ace625bf1bb9cd6ab422d72fb04f93c6fb" } } ], "extra": [ 1, 75, 120, 240, 163, 176, 18, 167, 14, 2, 32, 88, 86, 14, 123, 229, 74, 83, 115, 208, 134, 45, 214, 159, 52, 214, 116, 210, 238, 202, 165, 150, 85, 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