Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f05c27782f15c2a9649cdb3a2532ac1038f16c42827f4f57d1a5bd8eeb75b50

Tx prefix hash: a29fff1fbf1382c4f09bca6f1d818a2fb2b7bfbaedd6c1b22bed4478272fade2
Tx public key: fcacbd8c790b9817cd5657f4371421734e8a79db35556be1efc253ee0527ee55
Timestamp: 1588732504 Timestamp [UCT]: 2020-05-06 02:35:04 Age [y:d:h:m:s]: 04:279:07:09:23
Block: 98553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1116152 RingCT/type: yes/0
Extra: 01fcacbd8c790b9817cd5657f4371421734e8a79db35556be1efc253ee0527ee550211000000bb86362411000000000000000000

1 output(s) for total of 289.370172866000 dcy

stealth address amount amount idx
00: f383499e5e34a2e57463ead3cfc81a2ead96eb7dcaa0e83675ca2abca4f8176b 289.370172866000 174223 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": 98563, "vin": [ { "gen": { "height": 98553 } } ], "vout": [ { "amount": 289370172866, "target": { "key": "f383499e5e34a2e57463ead3cfc81a2ead96eb7dcaa0e83675ca2abca4f8176b" } } ], "extra": [ 1, 252, 172, 189, 140, 121, 11, 152, 23, 205, 86, 87, 244, 55, 20, 33, 115, 78, 138, 121, 219, 53, 85, 107, 225, 239, 194, 83, 238, 5, 39, 238, 85, 2, 17, 0, 0, 0, 187, 134, 54, 36, 17, 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