Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 838b6814c089bca51c82c6e2a859d0fcbef20b01ae87c9bfda763df8046cb558

Tx prefix hash: 42ed5a2ee0bb5d200fdd2fb25cda5eaef364e9cb181f8354964a3dc0ad02404a
Tx public key: 01ff84fdab88dc4749794fd20845008150283c913f65d9f892327c558c76d979
Timestamp: 1698380404 Timestamp [UCT]: 2023-10-27 04:20:04 Age [y:d:h:m:s]: 01:218:16:36:50
Block: 878535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417333 RingCT/type: yes/0
Extra: 0101ff84fdab88dc4749794fd20845008150283c913f65d9f892327c558c76d979021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.753440329000 dcy

stealth address amount amount idx
00: 0fe6b79700211b8fb921ce83ffcdadf72353f6901f026ad2defeff32cd49d096 0.753440329000 1333985 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": 878545, "vin": [ { "gen": { "height": 878535 } } ], "vout": [ { "amount": 753440329, "target": { "key": "0fe6b79700211b8fb921ce83ffcdadf72353f6901f026ad2defeff32cd49d096" } } ], "extra": [ 1, 1, 255, 132, 253, 171, 136, 220, 71, 73, 121, 79, 210, 8, 69, 0, 129, 80, 40, 60, 145, 63, 101, 217, 248, 146, 50, 124, 85, 140, 118, 217, 121, 2, 17, 0, 0, 0, 2, 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