Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 373a9850e21c05d3170eb472cb033fb70d30fe620fdfd9ccecd243dd7c33f9d4

Tx prefix hash: aa59e23f2dbddd24b65a7961cf2446d58ee8ad570ccd075f24c151cb1caf01e4
Tx public key: 0eea08c777b055df8ba114f3857eae96e6ab06f133eb2e9860e4885e182f6512
Timestamp: 1730994318 Timestamp [UCT]: 2024-11-07 15:45:18 Age [y:d:h:m:s]: 00:138:02:58:59
Block: 1148623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98534 RingCT/type: yes/0
Extra: 010eea08c777b055df8ba114f3857eae96e6ab06f133eb2e9860e4885e182f65120211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f903c9d62ef1d3a10983f1e979692407d8e02505671fc41bed590d2ac89369a8 0.600000000000 1633512 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": 1148633, "vin": [ { "gen": { "height": 1148623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f903c9d62ef1d3a10983f1e979692407d8e02505671fc41bed590d2ac89369a8" } } ], "extra": [ 1, 14, 234, 8, 199, 119, 176, 85, 223, 139, 161, 20, 243, 133, 126, 174, 150, 230, 171, 6, 241, 51, 235, 46, 152, 96, 228, 136, 94, 24, 47, 101, 18, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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