Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4106a4e92e5516041fbbe264d6f1b0c395f4e81c8dbaa30a831c872a160faff

Tx prefix hash: a0f64c362d9779b0a25d55f368da3e9731c855aa0c02b116e1fddad7786955d9
Tx public key: c696c306ea8c4044459963765aa4e80bb950201fc3996f651a4bf72326e7b9a1
Timestamp: 1722610496 Timestamp [UCT]: 2024-08-02 14:54:56 Age [y:d:h:m:s]: 00:244:17:02:12
Block: 1079199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174789 RingCT/type: yes/0
Extra: 01c696c306ea8c4044459963765aa4e80bb950201fc3996f651a4bf72326e7b9a102110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5661a56f4980af874de45979aec1c59f7f72da87084c1f71e9d0e9456cb5954a 0.600000000000 1552046 of 15

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": 1079209, "vin": [ { "gen": { "height": 1079199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5661a56f4980af874de45979aec1c59f7f72da87084c1f71e9d0e9456cb5954a" } } ], "extra": [ 1, 198, 150, 195, 6, 234, 140, 64, 68, 69, 153, 99, 118, 90, 164, 232, 11, 185, 80, 32, 31, 195, 153, 111, 101, 26, 75, 247, 35, 38, 231, 185, 161, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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