Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d21df262e9375bd85a0087a0e5160c3b750f11261d41792c721a824dc533b9bc

Tx prefix hash: 9afd9d91bc10c17797f2ef840cd34579e3da1bec35d4d3a6b2bba018e714a61f
Tx public key: d08b6f93d41b4d8d60d4b79dbf6803920a1eb6e14caec53167abfff45b285b7e
Timestamp: 1694276041 Timestamp [UCT]: 2023-09-09 16:14:01 Age [y:d:h:m:s]: 01:210:21:44:10
Block: 844475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411826 RingCT/type: yes/0
Extra: 01d08b6f93d41b4d8d60d4b79dbf6803920a1eb6e14caec53167abfff45b285b7e02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.977020849000 dcy

stealth address amount amount idx
00: 0a2c751737294ac97d6a1f6eaf20063b4c19dc7f5b9e981010731de56c933e8b 0.977020849000 1297785 of 0

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": 844485, "vin": [ { "gen": { "height": 844475 } } ], "vout": [ { "amount": 977020849, "target": { "key": "0a2c751737294ac97d6a1f6eaf20063b4c19dc7f5b9e981010731de56c933e8b" } } ], "extra": [ 1, 208, 139, 111, 147, 212, 27, 77, 141, 96, 212, 183, 157, 191, 104, 3, 146, 10, 30, 182, 225, 76, 174, 197, 49, 103, 171, 255, 244, 91, 40, 91, 126, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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