Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02e84979b156774f53473f608648427198ef9dc71a12fc26d5a9e07e54314645

Tx prefix hash: 0032d427f95049b4e120db5e2240482eca14d75535a0205f751222c4b1a2a3a6
Tx public key: e1c206140c8e8d9c5ead2bcb8a43b28313d55edb54020a9acfb0e5fab26740b2
Timestamp: 1707402275 Timestamp [UCT]: 2024-02-08 14:24:35 Age [y:d:h:m:s]: 01:042:08:19:32
Block: 953106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291310 RingCT/type: yes/0
Extra: 01e1c206140c8e8d9c5ead2bcb8a43b28313d55edb54020a9acfb0e5fab26740b2021100000001ec57b234000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe70e5263f37f8be924117ff6864486da360b5f006378426e0ddccf39b9feae5 0.600000000000 1412270 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": 953116, "vin": [ { "gen": { "height": 953106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe70e5263f37f8be924117ff6864486da360b5f006378426e0ddccf39b9feae5" } } ], "extra": [ 1, 225, 194, 6, 20, 12, 142, 141, 156, 94, 173, 43, 203, 138, 67, 178, 131, 19, 213, 94, 219, 84, 2, 10, 154, 207, 176, 229, 250, 178, 103, 64, 178, 2, 17, 0, 0, 0, 1, 236, 87, 178, 52, 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