Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0de2a2ed125569305fda14aa575e20d0ee88ee10d57373126ce5973f4ba7642c

Tx prefix hash: 489559b9bab98d3e1a7c57d74141e416ab19853b110985c0c2aed74f7a8695bd
Tx public key: e40a56e1ab2b87f1ea8ac3650e68d75c1fee1e236c765181c65cc66f6ad96787
Timestamp: 1735152230 Timestamp [UCT]: 2024-12-25 18:43:50 Age [y:d:h:m:s]: 00:121:18:09:47
Block: 1183055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86826 RingCT/type: yes/0
Extra: 01e40a56e1ab2b87f1ea8ac3650e68d75c1fee1e236c765181c65cc66f6ad96787021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1121b74697820b0de36a2ef7b973b1501f08565f61e59dd5e5872c6b487e8bf 0.600000000000 1669494 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": 1183065, "vin": [ { "gen": { "height": 1183055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1121b74697820b0de36a2ef7b973b1501f08565f61e59dd5e5872c6b487e8bf" } } ], "extra": [ 1, 228, 10, 86, 225, 171, 43, 135, 241, 234, 138, 195, 101, 14, 104, 215, 92, 31, 238, 30, 35, 108, 118, 81, 129, 198, 92, 198, 111, 106, 217, 103, 135, 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