Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 782f2203462e86941d5e78bf42293b90eabbc54a8f708608133f1f62e2890155

Tx prefix hash: 3a7927e7bfea70996170d0812087cf8c1099eac9a27efceeec305cb1009bc35f
Tx public key: d851d3ce3fb1c3c92ef82c161b7bc1a6a816fc4eb6a7767f5d344bc731e10aba
Timestamp: 1709195115 Timestamp [UCT]: 2024-02-29 08:25:15 Age [y:d:h:m:s]: 01:034:22:51:37
Block: 967987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285984 RingCT/type: yes/0
Extra: 01d851d3ce3fb1c3c92ef82c161b7bc1a6a816fc4eb6a7767f5d344bc731e10aba02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00a7100ad95293a2ffe4032ca50539c8e380a1642d4ea2b84c08f125a1a83fbc 0.600000000000 1427782 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": 967997, "vin": [ { "gen": { "height": 967987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00a7100ad95293a2ffe4032ca50539c8e380a1642d4ea2b84c08f125a1a83fbc" } } ], "extra": [ 1, 216, 81, 211, 206, 63, 177, 195, 201, 46, 248, 44, 22, 27, 123, 193, 166, 168, 22, 252, 78, 182, 167, 118, 127, 93, 52, 75, 199, 49, 225, 10, 186, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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