Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c22117d01b0e22362234ca908a55e957d4a72f132c25b1f598855e07becc4b2

Tx prefix hash: 4d09414959e62c7cd53c34be80271364c03280b7081a51f28bda706f8df84bc6
Tx public key: 6644caa4f401908dfc974618287a39c80cde7e70d56254899f6dbd9ddf0aa7ca
Timestamp: 1638765164 Timestamp [UCT]: 2021-12-06 04:32:44 Age [y:d:h:m:s]: 03:160:09:52:14
Block: 389423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 893384 RingCT/type: yes/0
Extra: 016644caa4f401908dfc974618287a39c80cde7e70d56254899f6dbd9ddf0aa7ca021100000001e9564d6f000000000000000000

1 output(s) for total of 31.454320723000 dcy

stealth address amount amount idx
00: 36eabfda9a40bfd60d68247a7ba43b0a888bb25bb30b64cd52ce9a6c126015a0 31.454320723000 784564 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": 389433, "vin": [ { "gen": { "height": 389423 } } ], "vout": [ { "amount": 31454320723, "target": { "key": "36eabfda9a40bfd60d68247a7ba43b0a888bb25bb30b64cd52ce9a6c126015a0" } } ], "extra": [ 1, 102, 68, 202, 164, 244, 1, 144, 141, 252, 151, 70, 24, 40, 122, 57, 200, 12, 222, 126, 112, 213, 98, 84, 137, 159, 109, 189, 157, 223, 10, 167, 202, 2, 17, 0, 0, 0, 1, 233, 86, 77, 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