Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cad519d6630ecda2624306885d152cd49f2dd4d08be0205c6e263f661e5cd57e

Tx prefix hash: ac40a3ee298f5018f42a6afb2dfb20b49e39194435e6ca34c3cd2777e996ba35
Tx public key: a9cd5d9bf60a8cc6bc9ad4ad463db89a6d227c51f5e3fcb77f597461ac6a6a8d
Timestamp: 1724105478 Timestamp [UCT]: 2024-08-19 22:11:18 Age [y:d:h:m:s]: 01:104:02:33:24
Block: 1091595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332885 RingCT/type: yes/0
Extra: 01a9cd5d9bf60a8cc6bc9ad4ad463db89a6d227c51f5e3fcb77f597461ac6a6a8d02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfb651593177ff60cb557bf3180ee4b31be370c54c5e5580ea51432a490b19c6 0.600000000000 1566228 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": 1091605, "vin": [ { "gen": { "height": 1091595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfb651593177ff60cb557bf3180ee4b31be370c54c5e5580ea51432a490b19c6" } } ], "extra": [ 1, 169, 205, 93, 155, 246, 10, 140, 198, 188, 154, 212, 173, 70, 61, 184, 154, 109, 34, 124, 81, 245, 227, 252, 183, 127, 89, 116, 97, 172, 106, 106, 141, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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