Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b59d8975b21d08390e48867588e715b27f7603a112b67d4bc244f2e80a89548

Tx prefix hash: 95d63e4c7e92dbf9a5aefc6553e487b3299bf958f17b576ac489addc82d55e9b
Tx public key: 028c712f5275d74d89d77a12e6e7d7447cbfa3ac7f7a1f6350f076770aa36642
Timestamp: 1708281653 Timestamp [UCT]: 2024-02-18 18:40:53 Age [y:d:h:m:s]: 01:050:14:40:16
Block: 960410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297200 RingCT/type: yes/0
Extra: 01028c712f5275d74d89d77a12e6e7d7447cbfa3ac7f7a1f6350f076770aa366420211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65a56d36ed4096f01b6dad58f7d06b9f8174f777785a6be9745a9a4a6bd4b5a 0.600000000000 1419973 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": 960420, "vin": [ { "gen": { "height": 960410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65a56d36ed4096f01b6dad58f7d06b9f8174f777785a6be9745a9a4a6bd4b5a" } } ], "extra": [ 1, 2, 140, 113, 47, 82, 117, 215, 77, 137, 215, 122, 18, 230, 231, 215, 68, 124, 191, 163, 172, 127, 122, 31, 99, 80, 240, 118, 119, 10, 163, 102, 66, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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