Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dea3f3da92a26ca2d9fac86a94384f0a8a1ea237e9ff8c07dace1b15af4d3237

Tx prefix hash: 8f6f7e0bb2f7c1777f1f8b15dcdff5dacce2948130597a5fc5901d5475f23daf
Tx public key: 4dcdb5226d356c881967fe74ec9e19948c1f350b16d429aa4d81859b92626631
Timestamp: 1702326000 Timestamp [UCT]: 2023-12-11 20:20:00 Age [y:d:h:m:s]: 01:138:01:41:59
Block: 911037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359829 RingCT/type: yes/0
Extra: 014dcdb5226d356c881967fe74ec9e19948c1f350b16d429aa4d81859b9262663102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3351863f96ae4f094849acae92ccfdbc1dca5e1a36890a9fa8792d30b97df52 0.600000000000 1368212 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": 911047, "vin": [ { "gen": { "height": 911037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3351863f96ae4f094849acae92ccfdbc1dca5e1a36890a9fa8792d30b97df52" } } ], "extra": [ 1, 77, 205, 181, 34, 109, 53, 108, 136, 25, 103, 254, 116, 236, 158, 25, 148, 140, 31, 53, 11, 22, 212, 41, 170, 77, 129, 133, 155, 146, 98, 102, 49, 2, 17, 0, 0, 0, 2, 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