Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42b906602e4b5765d6c43fa3d83c8467aba7ba63d461324b39aa1cfe4bfc00f7

Tx prefix hash: 79683d443ebb2ad8821df7f1cf24d75f839244a099f7af15b8be8cd29e961f32
Tx public key: ec08b44a3078ef3f07c84291c3820d8f25dbdfb52936a2f5e729b468b2d3f479
Timestamp: 1738858520 Timestamp [UCT]: 2025-02-06 16:15:20 Age [y:d:h:m:s]: 00:287:05:33:19
Block: 1213477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203035 RingCT/type: yes/0
Extra: 01ec08b44a3078ef3f07c84291c3820d8f25dbdfb52936a2f5e729b468b2d3f479021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ea16bddef44e9d195f7d8474481caed751c4b33d1723561db612c2946080c93 0.600000000000 1700256 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": 1213487, "vin": [ { "gen": { "height": 1213477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ea16bddef44e9d195f7d8474481caed751c4b33d1723561db612c2946080c93" } } ], "extra": [ 1, 236, 8, 180, 74, 48, 120, 239, 63, 7, 200, 66, 145, 195, 130, 13, 143, 37, 219, 223, 181, 41, 54, 162, 245, 231, 41, 180, 104, 178, 211, 244, 121, 2, 17, 0, 0, 0, 2, 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