Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d1700b886d91a4a4f1e2e8397b1f630e102e58f09a18b0b81b60da3e040b83b

Tx prefix hash: a0284c001d404cd0cb2bfa8be80f174ced6cc0fd84a2762f067b1c013f1cea0a
Tx public key: aef636af90df55a357dce23ed94a8fca016cebfce4a7a8b96aa222ad6c3a60cc
Timestamp: 1657202080 Timestamp [UCT]: 2022-07-07 13:54:40 Age [y:d:h:m:s]: 02:183:11:00:40
Block: 538644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 652464 RingCT/type: yes/0
Extra: 01aef636af90df55a357dce23ed94a8fca016cebfce4a7a8b96aa222ad6c3a60cc02110000000233af99f4000000000000000000

1 output(s) for total of 10.075090947000 dcy

stealth address amount amount idx
00: 4e6c3e82e32da246dc13e0758c3da6ee920e8e160f830d5cc19a510c2b966c4e 10.075090947000 968669 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": 538654, "vin": [ { "gen": { "height": 538644 } } ], "vout": [ { "amount": 10075090947, "target": { "key": "4e6c3e82e32da246dc13e0758c3da6ee920e8e160f830d5cc19a510c2b966c4e" } } ], "extra": [ 1, 174, 246, 54, 175, 144, 223, 85, 163, 87, 220, 226, 62, 217, 74, 143, 202, 1, 108, 235, 252, 228, 167, 168, 185, 106, 162, 34, 173, 108, 58, 96, 204, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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