Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98d759d21ac2db1a4ecd5bd57472a94b7994b0ea2a5027f8982b8db5fbdbab16

Tx prefix hash: c2c1d00e6b279ff833999107e4238a56b11985e1dfb00ed4cdbd418d514fe74c
Tx public key: 38ff65244179feff9e553b16c0c8888a5a1c75c359553b10e19a46743b06f281
Timestamp: 1581912369 Timestamp [UCT]: 2020-02-17 04:06:09 Age [y:d:h:m:s]: 05:023:14:23:16
Block: 66511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1169922 RingCT/type: yes/0
Extra: 0138ff65244179feff9e553b16c0c8888a5a1c75c359553b10e19a46743b06f281021100000001d81c26c0000000000000000000

1 output(s) for total of 369.506647427000 dcy

stealth address amount amount idx
00: aca0b3083d2d83ab45fbb497c6324faeb5d9b49fc43828bc1c737564032c19b7 369.506647427000 122518 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": 66521, "vin": [ { "gen": { "height": 66511 } } ], "vout": [ { "amount": 369506647427, "target": { "key": "aca0b3083d2d83ab45fbb497c6324faeb5d9b49fc43828bc1c737564032c19b7" } } ], "extra": [ 1, 56, 255, 101, 36, 65, 121, 254, 255, 158, 85, 59, 22, 192, 200, 136, 138, 90, 28, 117, 195, 89, 85, 59, 16, 225, 154, 70, 116, 59, 6, 242, 129, 2, 17, 0, 0, 0, 1, 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