Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c53fcc38060639d3fbc42d43bc2501644b05c9f301779d311551d3eadd5d2bbf

Tx prefix hash: 1f0933f9fc76001944ad04452c8dfcbca8b403306973583d8f25238e2e444865
Tx public key: 0bdf0ae81f59988cc1d47db090a073de3c2f8b4be5521f92f59b2ff446dcc888
Timestamp: 1662670403 Timestamp [UCT]: 2022-09-08 20:53:23 Age [y:d:h:m:s]: 02:208:05:25:46
Block: 583705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 670105 RingCT/type: yes/0
Extra: 010bdf0ae81f59988cc1d47db090a073de3c2f8b4be5521f92f59b2ff446dcc888021100000002e4c64a6f000000000000000000

1 output(s) for total of 7.144027381000 dcy

stealth address amount amount idx
00: 0fc06d7b8a049a77d68dff8bf2dfb0647ccfd842893db0c255edf1ab1ed42569 7.144027381000 1017549 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": 583715, "vin": [ { "gen": { "height": 583705 } } ], "vout": [ { "amount": 7144027381, "target": { "key": "0fc06d7b8a049a77d68dff8bf2dfb0647ccfd842893db0c255edf1ab1ed42569" } } ], "extra": [ 1, 11, 223, 10, 232, 31, 89, 152, 140, 193, 212, 125, 176, 144, 160, 115, 222, 60, 47, 139, 75, 229, 82, 31, 146, 245, 155, 47, 244, 70, 220, 200, 136, 2, 17, 0, 0, 0, 2, 228, 198, 74, 111, 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