Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 800ed7953ce65e57895d9ead0cb48767ea2a78e8bc6875cfcdc072c7bae48753

Tx prefix hash: 44681dd1926aab80b562cb12a0344a9137f4a3c8b3fd36ef331216bbcf88ab49
Tx public key: 4f1e84490bc95f27709d9b4f4ddb93f149d64865822cb4d61342105aee4cb820
Timestamp: 1673097002 Timestamp [UCT]: 2023-01-07 13:10:02 Age [y:d:h:m:s]: 02:093:23:38:54
Block: 669564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588858 RingCT/type: yes/0
Extra: 014f1e84490bc95f27709d9b4f4ddb93f149d64865822cb4d61342105aee4cb82002110000000252542ceb000000000000000000

1 output(s) for total of 3.710705403000 dcy

stealth address amount amount idx
00: d1f1ef8267f7c2c96ec550f0879c77c4a7da6d1da6d04f3e0b458ca500325433 3.710705403000 1110905 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": 669574, "vin": [ { "gen": { "height": 669564 } } ], "vout": [ { "amount": 3710705403, "target": { "key": "d1f1ef8267f7c2c96ec550f0879c77c4a7da6d1da6d04f3e0b458ca500325433" } } ], "extra": [ 1, 79, 30, 132, 73, 11, 201, 95, 39, 112, 157, 155, 79, 77, 219, 147, 241, 73, 214, 72, 101, 130, 44, 180, 214, 19, 66, 16, 90, 238, 76, 184, 32, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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