Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69b4aab14a95b85b9d89f86d47fcc83a70c2ed542fba618f297b77bd5a03df73

Tx prefix hash: 6d66cfc44d8c128841d0d672ae53f5907509f4711bde987bb35f37d0c3ef11e9
Tx public key: e852dcdbecaecab16cad58eaae54d4cbab31e9f0fb07a5cc9fe2cf8db6c83bee
Timestamp: 1675083966 Timestamp [UCT]: 2023-01-30 13:06:06 Age [y:d:h:m:s]: 02:106:08:24:18
Block: 686056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597670 RingCT/type: yes/0
Extra: 01e852dcdbecaecab16cad58eaae54d4cbab31e9f0fb07a5cc9fe2cf8db6c83bee0211000000035029cbac000000000000000000

1 output(s) for total of 3.271987308000 dcy

stealth address amount amount idx
00: e7bd9b85a53689530520b34e7a1fcf4b5f82eca2ebabdebbae487838c565bedd 3.271987308000 1128517 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": 686066, "vin": [ { "gen": { "height": 686056 } } ], "vout": [ { "amount": 3271987308, "target": { "key": "e7bd9b85a53689530520b34e7a1fcf4b5f82eca2ebabdebbae487838c565bedd" } } ], "extra": [ 1, 232, 82, 220, 219, 236, 174, 202, 177, 108, 173, 88, 234, 174, 84, 212, 203, 171, 49, 233, 240, 251, 7, 165, 204, 159, 226, 207, 141, 182, 200, 59, 238, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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