Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0898ce6e5960f2203e4845349a3ab95edb9ab84c42d97b70296cdf36067c1976

Tx prefix hash: 0ab639e4faf47c2ecaedade980083ca3b01e85e021b65665c4982e772277ad4a
Tx public key: 99e0bacbf8ca32d101334970147b214a4c9fdc1a1dbe665b896e38cb0fcb829d
Timestamp: 1696223986 Timestamp [UCT]: 2023-10-02 05:19:46 Age [y:d:h:m:s]: 01:107:11:34:32
Block: 860647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338086 RingCT/type: yes/0
Extra: 0199e0bacbf8ca32d101334970147b214a4c9fdc1a1dbe665b896e38cb0fcb829d021100000002bfa22221000000000000000000

1 output(s) for total of 0.863613174000 dcy

stealth address amount amount idx
00: c4e2117e9660e589f07f0e16d021f24baec1ed2b3edd31d5b5e3dff3bccaba44 0.863613174000 1314939 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": 860657, "vin": [ { "gen": { "height": 860647 } } ], "vout": [ { "amount": 863613174, "target": { "key": "c4e2117e9660e589f07f0e16d021f24baec1ed2b3edd31d5b5e3dff3bccaba44" } } ], "extra": [ 1, 153, 224, 186, 203, 248, 202, 50, 209, 1, 51, 73, 112, 20, 123, 33, 74, 76, 159, 220, 26, 29, 190, 102, 91, 137, 110, 56, 203, 15, 203, 130, 157, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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