Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a13a9e07fbab576dacecdf538d9f313b5a32c40b1f1e0a91a463a4c5928f7cf

Tx prefix hash: 3d6303b0bd22272ea365683c8680d3596db28fc008809ab5db8117aaa0091d2a
Tx public key: 7d7c0a0694be58a4b82de64d3550773b79774b4f62a756b74c4b99aa71edb422
Timestamp: 1736020841 Timestamp [UCT]: 2025-01-04 20:00:41 Age [y:d:h:m:s]: 00:346:16:44:48
Block: 1190246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245327 RingCT/type: yes/0
Extra: 017d7c0a0694be58a4b82de64d3550773b79774b4f62a756b74c4b99aa71edb422021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3c8cad2f87213bc559261414a9dd466a223d24222d948e9c14a0c9d37126f19 0.600000000000 1676761 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": 1190256, "vin": [ { "gen": { "height": 1190246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3c8cad2f87213bc559261414a9dd466a223d24222d948e9c14a0c9d37126f19" } } ], "extra": [ 1, 125, 124, 10, 6, 148, 190, 88, 164, 184, 45, 230, 77, 53, 80, 119, 59, 121, 119, 75, 79, 98, 167, 86, 183, 76, 75, 153, 170, 113, 237, 180, 34, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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