Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b656da4f24bdee2f92a116e865db0354e9a8e64394dd1099b03a81579d2b101

Tx prefix hash: e8b60894fd1983793e6c95fabdb63e5b45c12656514c16606c5781a34f9b4178
Tx public key: 1f36ecb1e77b2abdfbcc146c8d2fe91c930059222eaee9faa128faa46f9ebaf7
Timestamp: 1702207439 Timestamp [UCT]: 2023-12-10 11:23:59 Age [y:d:h:m:s]: 01:171:02:28:32
Block: 910048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383482 RingCT/type: yes/0
Extra: 011f36ecb1e77b2abdfbcc146c8d2fe91c930059222eaee9faa128faa46f9ebaf702110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c6d458a1c743f8f0c838f829653b9e05d2c1349b68601468b0acc89bad2e7cf 0.600000000000 1367189 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": 910058, "vin": [ { "gen": { "height": 910048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c6d458a1c743f8f0c838f829653b9e05d2c1349b68601468b0acc89bad2e7cf" } } ], "extra": [ 1, 31, 54, 236, 177, 231, 123, 42, 189, 251, 204, 20, 108, 141, 47, 233, 28, 147, 0, 89, 34, 46, 174, 233, 250, 161, 40, 250, 164, 111, 158, 186, 247, 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