Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 237f91ceb14b8c1bd2c0c98277681ad05b2d0fc3afc83be7eb6e9cfa6b5e6343

Tx prefix hash: 3169ad1de2a77dc6798a777957f65978f282c1e6ec874e407dd5df7e05a51da5
Tx public key: 04d717741f3707ffe11753ca61c3eb5c723d701304747d1e39d57f5de6f8d3b5
Timestamp: 1706872489 Timestamp [UCT]: 2024-02-02 11:14:49 Age [y:d:h:m:s]: 01:272:12:09:01
Block: 948719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453535 RingCT/type: yes/0
Extra: 0104d717741f3707ffe11753ca61c3eb5c723d701304747d1e39d57f5de6f8d3b50211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 710057fda8d3d24f9d8d610a88bd95b70f6b5b01fe77fdf53dd7c31e336c8f5c 0.600000000000 1407185 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": 948729, "vin": [ { "gen": { "height": 948719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "710057fda8d3d24f9d8d610a88bd95b70f6b5b01fe77fdf53dd7c31e336c8f5c" } } ], "extra": [ 1, 4, 215, 23, 116, 31, 55, 7, 255, 225, 23, 83, 202, 97, 195, 235, 92, 114, 61, 112, 19, 4, 116, 125, 30, 57, 213, 127, 93, 230, 248, 211, 181, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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