Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76530f75f71ccf9ae3054f74ef376ec0b4ff3164a31ccdb229197b4d4f9616bb

Tx prefix hash: 58350495164ae32b1d733d246254d52e3d23ef512fdeae41bd1cfb2f2f38143a
Tx public key: 0aa806a61042ba226b42a4efb7c4475e0bd2e5bfcce40a4f11a6aa02aedaff76
Timestamp: 1672586236 Timestamp [UCT]: 2023-01-01 15:17:16 Age [y:d:h:m:s]: 02:106:20:39:55
Block: 665337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598067 RingCT/type: yes/0
Extra: 010aa806a61042ba226b42a4efb7c4475e0bd2e5bfcce40a4f11a6aa02aedaff760211000000025029cbac000000000000000000

1 output(s) for total of 3.832364614000 dcy

stealth address amount amount idx
00: feff1b3d5dfa4c0e6c08b89e75ad69f64278b4999e4b0f1420f598d6ee16a936 3.832364614000 1106374 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": 665347, "vin": [ { "gen": { "height": 665337 } } ], "vout": [ { "amount": 3832364614, "target": { "key": "feff1b3d5dfa4c0e6c08b89e75ad69f64278b4999e4b0f1420f598d6ee16a936" } } ], "extra": [ 1, 10, 168, 6, 166, 16, 66, 186, 34, 107, 66, 164, 239, 183, 196, 71, 94, 11, 210, 229, 191, 204, 228, 10, 79, 17, 166, 170, 2, 174, 218, 255, 118, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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