Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e24ee40efb399b845a4a5b91ad4773e0bb0096e8874dc53fff947937fd637a2

Tx prefix hash: 2374ea0bca19b088e8c75733573d1f84bc75608fc27e717b894c7192b41c8340
Tx public key: 446bc5d250474371c160747ee8259861c9a5d0a23861ef186115fa2d261795e5
Timestamp: 1581379758 Timestamp [UCT]: 2020-02-11 00:09:18 Age [y:d:h:m:s]: 04:282:05:41:55
Block: 62465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093728 RingCT/type: yes/0
Extra: 01446bc5d250474371c160747ee8259861c9a5d0a23861ef186115fa2d261795e5021100000003d81c26c0000000000000000000

1 output(s) for total of 381.090690110000 dcy

stealth address amount amount idx
00: 3f0b60945c2e32b6dee4b2cefeff1c937cee7d45a7c879dcf87847bc2e468c8d 381.090690110000 115239 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": 62475, "vin": [ { "gen": { "height": 62465 } } ], "vout": [ { "amount": 381090690110, "target": { "key": "3f0b60945c2e32b6dee4b2cefeff1c937cee7d45a7c879dcf87847bc2e468c8d" } } ], "extra": [ 1, 68, 107, 197, 210, 80, 71, 67, 113, 193, 96, 116, 126, 232, 37, 152, 97, 201, 165, 208, 162, 56, 97, 239, 24, 97, 21, 250, 45, 38, 23, 149, 229, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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