Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f925a4465be2563aad7f129a9d26b6315c4c5c9907251ba861ffd455b23017e5

Tx prefix hash: 9c4b40818915a93da0ea4f7500e4d01ff4312c66e5475efb1b80f0948f23e412
Tx public key: ff960e3d9a9ea02ae2bc6d5e3e4214def4f30bba3fdb1b1feb5613be75996b29
Timestamp: 1704239502 Timestamp [UCT]: 2024-01-02 23:51:42 Age [y:d:h:m:s]: 01:307:22:36:35
Block: 926885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478898 RingCT/type: yes/0
Extra: 01ff960e3d9a9ea02ae2bc6d5e3e4214def4f30bba3fdb1b1feb5613be75996b290211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23eacd8bde7dc6b75fdf81300cc4f41b0516bfeb389e9ddf528fb794db42d6f9 0.600000000000 1384685 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": 926895, "vin": [ { "gen": { "height": 926885 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23eacd8bde7dc6b75fdf81300cc4f41b0516bfeb389e9ddf528fb794db42d6f9" } } ], "extra": [ 1, 255, 150, 14, 61, 154, 158, 160, 42, 226, 188, 109, 94, 62, 66, 20, 222, 244, 243, 11, 186, 63, 219, 27, 31, 235, 86, 19, 190, 117, 153, 107, 41, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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