Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74e9f68495a7d25b245b24db934c230f396629c3ec7a3677f1a70a52ae1577a6

Tx prefix hash: d83b17484177f93989eeda7a955b08c383768fa225e2d2df1649096a2aabebce
Tx public key: 55414174af1c7fd9527d364902058fae517e8a541615547f263f90d9d0506b72
Timestamp: 1645500430 Timestamp [UCT]: 2022-02-22 03:27:10 Age [y:d:h:m:s]: 02:305:05:01:07
Block: 443785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737562 RingCT/type: yes/0
Extra: 0155414174af1c7fd9527d364902058fae517e8a541615547f263f90d9d0506b720211000000104da16a3a000000000000000000

1 output(s) for total of 20.775733175000 dcy

stealth address amount amount idx
00: c47aff4d764ba307072c0e6edb1a26a072d8ec2d5c9c16cb887a23c28384c5e1 20.775733175000 856904 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": 443795, "vin": [ { "gen": { "height": 443785 } } ], "vout": [ { "amount": 20775733175, "target": { "key": "c47aff4d764ba307072c0e6edb1a26a072d8ec2d5c9c16cb887a23c28384c5e1" } } ], "extra": [ 1, 85, 65, 65, 116, 175, 28, 127, 217, 82, 125, 54, 73, 2, 5, 143, 174, 81, 126, 138, 84, 22, 21, 84, 127, 38, 63, 144, 217, 208, 80, 107, 114, 2, 17, 0, 0, 0, 16, 77, 161, 106, 58, 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