Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5137b90eb8a6ce560d498b9680f5d6985305a90db2ed5b4d334aab9c4f963d7

Tx prefix hash: 91807ec9c42e4cd25c15d69f429eeb487450476fe69950b928d9115c4fa97ad5
Tx public key: 3c9a98bdb84e3520b9f13a960304cad951bf4c468ca067170a7d30f2b0f46f3b
Timestamp: 1723077870 Timestamp [UCT]: 2024-08-08 00:44:30 Age [y:d:h:m:s]: 01:084:13:43:48
Block: 1083070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318917 RingCT/type: yes/0
Extra: 013c9a98bdb84e3520b9f13a960304cad951bf4c468ca067170a7d30f2b0f46f3b02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 791dd25edb15d072c74a433629a24ad50f6f9ab26dea073247c427f149fb659c 0.600000000000 1556905 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": 1083080, "vin": [ { "gen": { "height": 1083070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "791dd25edb15d072c74a433629a24ad50f6f9ab26dea073247c427f149fb659c" } } ], "extra": [ 1, 60, 154, 152, 189, 184, 78, 53, 32, 185, 241, 58, 150, 3, 4, 202, 217, 81, 191, 76, 70, 140, 160, 103, 23, 10, 125, 48, 242, 176, 244, 111, 59, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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