Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 809cceb11e7aa789d618edc8c9b680f3a5262c944e38b5ed33c6bdbf2d0d6509

Tx prefix hash: 4f46c7e75946728a1c4a756801b1cb0239f50668836d520956b0c2d3d1917f58
Tx public key: 16501ff1ea24f57ec33b689ed947e6078ee8ff7bc5bf6778bfdde83501e2f5b5
Timestamp: 1720745837 Timestamp [UCT]: 2024-07-12 00:57:17 Age [y:d:h:m:s]: 00:285:17:47:15
Block: 1063747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204150 RingCT/type: yes/0
Extra: 0116501ff1ea24f57ec33b689ed947e6078ee8ff7bc5bf6778bfdde83501e2f5b502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9984bd1ff75c50c01d8fdbaea39b2a03423b2838a5f704cb9c23855bf59c26c 0.600000000000 1534264 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": 1063757, "vin": [ { "gen": { "height": 1063747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9984bd1ff75c50c01d8fdbaea39b2a03423b2838a5f704cb9c23855bf59c26c" } } ], "extra": [ 1, 22, 80, 31, 241, 234, 36, 245, 126, 195, 59, 104, 158, 217, 71, 230, 7, 142, 232, 255, 123, 197, 191, 103, 120, 191, 221, 232, 53, 1, 226, 245, 181, 2, 17, 0, 0, 0, 2, 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