Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e6d26843f8c9160cddb3e54cdb277aea90245c13ff51ef828f51d5edc823d6f

Tx prefix hash: fdb99cd1f5b2660bd57a6213a083cfffc1d4d2ac5dc6379dc989560a927bba15
Tx public key: 7a3174efbcfc8f270f40c82be90089fd833f488879d3212839fce8f7c989b236
Timestamp: 1645529254 Timestamp [UCT]: 2022-02-22 11:27:34 Age [y:d:h:m:s]: 02:268:06:08:58
Block: 444020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 711083 RingCT/type: yes/0
Extra: 017a3174efbcfc8f270f40c82be90089fd833f488879d3212839fce8f7c989b236021100000001a8c141c5000000000000000000

1 output(s) for total of 20.738517433000 dcy

stealth address amount amount idx
00: a15e4788d66616d56d76d83f745724bd4ff1c15a75a785577e6a404cd01bc97b 20.738517433000 857195 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": 444030, "vin": [ { "gen": { "height": 444020 } } ], "vout": [ { "amount": 20738517433, "target": { "key": "a15e4788d66616d56d76d83f745724bd4ff1c15a75a785577e6a404cd01bc97b" } } ], "extra": [ 1, 122, 49, 116, 239, 188, 252, 143, 39, 15, 64, 200, 43, 233, 0, 137, 253, 131, 63, 72, 136, 121, 211, 33, 40, 57, 252, 232, 247, 201, 137, 178, 54, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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