Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f064e5b99c7f5b72cb9216ad6f69c05d3f65b32f9d35a03e75720734a26ca72

Tx prefix hash: 8eb43829304925d0408fc73a195b2f31593330ab1265840653543039c0bb3324
Tx public key: cf81d6a9725619bd3d35e9748b2f43e482aab307730d31ebd73239a6a0e98ab8
Timestamp: 1613276186 Timestamp [UCT]: 2021-02-14 04:16:26 Age [y:d:h:m:s]: 03:318:15:22:37
Block: 198466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 986749 RingCT/type: yes/0
Extra: 01cf81d6a9725619bd3d35e9748b2f43e482aab307730d31ebd73239a6a0e98ab8021100000023a45716b1000000000000000000

1 output(s) for total of 135.020707779000 dcy

stealth address amount amount idx
00: 67138349d4f9e8ab3a13c033b0576951b72a86512e041778ca11e7b070912bba 135.020707779000 406340 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": 198476, "vin": [ { "gen": { "height": 198466 } } ], "vout": [ { "amount": 135020707779, "target": { "key": "67138349d4f9e8ab3a13c033b0576951b72a86512e041778ca11e7b070912bba" } } ], "extra": [ 1, 207, 129, 214, 169, 114, 86, 25, 189, 61, 53, 233, 116, 139, 47, 67, 228, 130, 170, 179, 7, 115, 13, 49, 235, 215, 50, 57, 166, 160, 233, 138, 184, 2, 17, 0, 0, 0, 35, 164, 87, 22, 177, 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