Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a24c51dbaf8b92021224838a6f7feebf9b9dd919ff523399fc6f12b2f522b4e1

Tx prefix hash: 6a6f86a2020383b7015ffea3ab22763b521bde129f59addbe95ec811d62f7e00
Tx public key: 189a1e208987abbf3dc56aaf63b9290ed943ab7bf2cb0da27d41f16b95702488
Timestamp: 1704150880 Timestamp [UCT]: 2024-01-01 23:14:40 Age [y:d:h:m:s]: 01:172:20:07:43
Block: 926153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384471 RingCT/type: yes/0
Extra: 01189a1e208987abbf3dc56aaf63b9290ed943ab7bf2cb0da27d41f16b957024880211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2495b540a4d2a38971c6f87a60b49a0cbf05f2dc9faba360fb51d83a5d3916bb 0.600000000000 1383927 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": 926163, "vin": [ { "gen": { "height": 926153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2495b540a4d2a38971c6f87a60b49a0cbf05f2dc9faba360fb51d83a5d3916bb" } } ], "extra": [ 1, 24, 154, 30, 32, 137, 135, 171, 191, 61, 197, 106, 175, 99, 185, 41, 14, 217, 67, 171, 123, 242, 203, 13, 162, 125, 65, 241, 107, 149, 112, 36, 136, 2, 17, 0, 0, 0, 5, 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