Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27b1d6a2ed12b2bde1fc09e811676839deedf7d9f704b8e77fbeb283da3a54f3

Tx prefix hash: f89b5b96a493d6a70efa28a9960627cfd1e2788609e4a238dfd18f64eca277e2
Tx public key: ef9ac357565e229d48ff964ee7a5bbcc4928654bcbd4d45ccae5e4495739f823
Timestamp: 1585413849 Timestamp [UCT]: 2020-03-28 16:44:09 Age [y:d:h:m:s]: 04:232:15:44:06
Block: 88724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1065398 RingCT/type: yes/0
Extra: 01ef9ac357565e229d48ff964ee7a5bbcc4928654bcbd4d45ccae5e4495739f823021100000003a86a1a65000000000000000000

1 output(s) for total of 311.904279874000 dcy

stealth address amount amount idx
00: ce045f903b2c536795be2408a0d184733a2da9d4ec13c180366c5b9ff87542b3 311.904279874000 159462 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": 88734, "vin": [ { "gen": { "height": 88724 } } ], "vout": [ { "amount": 311904279874, "target": { "key": "ce045f903b2c536795be2408a0d184733a2da9d4ec13c180366c5b9ff87542b3" } } ], "extra": [ 1, 239, 154, 195, 87, 86, 94, 34, 157, 72, 255, 150, 78, 231, 165, 187, 204, 73, 40, 101, 75, 203, 212, 212, 92, 202, 229, 228, 73, 87, 57, 248, 35, 2, 17, 0, 0, 0, 3, 168, 106, 26, 101, 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