Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad8da44e80886231fb2269d3cd99d9e84125bf86ec8f4354f98897b1c383702c

Tx prefix hash: bd2139c6beb0faf0cd78e2833dca1afa7a29eacd7759dddb07656e414c361d21
Tx public key: 056c6078763709e473419e1c84f766ec1268ed0edfe2fb7d05e4a0b0885bf2c5
Timestamp: 1681211700 Timestamp [UCT]: 2023-04-11 11:15:00 Age [y:d:h:m:s]: 01:275:20:34:24
Block: 736219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458667 RingCT/type: yes/0
Extra: 01056c6078763709e473419e1c84f766ec1268ed0edfe2fb7d05e4a0b0885bf2c50211000000045029cbac000000000000000000

1 output(s) for total of 2.231521406000 dcy

stealth address amount amount idx
00: 597620e068d41e2d42eb3c3a52a70e2d881b04a2ba161a5b90fb1153629891ea 2.231521406000 1182636 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": 736229, "vin": [ { "gen": { "height": 736219 } } ], "vout": [ { "amount": 2231521406, "target": { "key": "597620e068d41e2d42eb3c3a52a70e2d881b04a2ba161a5b90fb1153629891ea" } } ], "extra": [ 1, 5, 108, 96, 120, 118, 55, 9, 228, 115, 65, 158, 28, 132, 247, 102, 236, 18, 104, 237, 14, 223, 226, 251, 125, 5, 228, 160, 176, 136, 91, 242, 197, 2, 17, 0, 0, 0, 4, 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