Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa42cbca010abba6741eaa63971c7133db53025b81e06c4a5e82e0a05a51edad

Tx prefix hash: b685a536873ea6024ee35e380c13e6bb490c708941501f6d82eac47dfbbf2761
Tx public key: 0727b550df303bbbfdc035ca805fa90c695f14c6666f4395cd8db6bc7e80d1d1
Timestamp: 1697248009 Timestamp [UCT]: 2023-10-14 01:46:49 Age [y:d:h:m:s]: 01:179:12:36:37
Block: 869131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389342 RingCT/type: yes/0
Extra: 010727b550df303bbbfdc035ca805fa90c695f14c6666f4395cd8db6bc7e80d1d1021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.809483931000 dcy

stealth address amount amount idx
00: e8896e96ccca71387287dc2ff8bedab610c6d7a0392d010c1f4d16147a67f293 0.809483931000 1323966 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": 869141, "vin": [ { "gen": { "height": 869131 } } ], "vout": [ { "amount": 809483931, "target": { "key": "e8896e96ccca71387287dc2ff8bedab610c6d7a0392d010c1f4d16147a67f293" } } ], "extra": [ 1, 7, 39, 181, 80, 223, 48, 59, 187, 253, 192, 53, 202, 128, 95, 169, 12, 105, 95, 20, 198, 102, 111, 67, 149, 205, 141, 182, 188, 126, 128, 209, 209, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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