Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0510d48a77df2bce67d0ee152ec0c0b3cc9e6d775c1a053ac03f837f4472312f

Tx prefix hash: e536d1418a3af8604f7fe9ebf1dc18c182d79123f5db1d44e79c7a5706912e7b
Tx public key: 898ca0bf6ed2cb59697f1b66abfce5bf057eef2d289ede883021301722ac9716
Timestamp: 1694193715 Timestamp [UCT]: 2023-09-08 17:21:55 Age [y:d:h:m:s]: 02:058:04:33:18
Block: 843791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 561268 RingCT/type: yes/0
Extra: 01898ca0bf6ed2cb59697f1b66abfce5bf057eef2d289ede883021301722ac971602110000000275e3f0e9000000000000000000

1 output(s) for total of 0.990802784000 dcy

stealth address amount amount idx
00: 17b378528ee2ce432818e172b0d9001a74ea225270d97161276aa7cd8bfe35ae 0.990802784000 1297057 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": 843801, "vin": [ { "gen": { "height": 843791 } } ], "vout": [ { "amount": 990802784, "target": { "key": "17b378528ee2ce432818e172b0d9001a74ea225270d97161276aa7cd8bfe35ae" } } ], "extra": [ 1, 137, 140, 160, 191, 110, 210, 203, 89, 105, 127, 27, 102, 171, 252, 229, 191, 5, 126, 239, 45, 40, 158, 222, 136, 48, 33, 48, 23, 34, 172, 151, 22, 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