Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cf5fe702d48e3c75a33f4c82f1023d5e6d08d9807d6261d5c48bcb63a5a9133

Tx prefix hash: 0a5c10d1bcd4448889fe6a7b6bd4b5b7262e63e56b91cdcbfb7a5dd06b7d8b9d
Tx public key: fb39e9ba8440347404113f4204c0e69fa00f3c41fb17eb1cf91f1798e19d25dd
Timestamp: 1698622729 Timestamp [UCT]: 2023-10-29 23:38:49 Age [y:d:h:m:s]: 01:117:19:45:52
Block: 880543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345159 RingCT/type: yes/0
Extra: 01fb39e9ba8440347404113f4204c0e69fa00f3c41fb17eb1cf91f1798e19d25dd021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.741985677000 dcy

stealth address amount amount idx
00: 11cc9c0f35f24b7e6486b22a1eb5750f0bd5fcced940604f4ee3fba637c5d445 0.741985677000 1336101 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": 880553, "vin": [ { "gen": { "height": 880543 } } ], "vout": [ { "amount": 741985677, "target": { "key": "11cc9c0f35f24b7e6486b22a1eb5750f0bd5fcced940604f4ee3fba637c5d445" } } ], "extra": [ 1, 251, 57, 233, 186, 132, 64, 52, 116, 4, 17, 63, 66, 4, 192, 230, 159, 160, 15, 60, 65, 251, 23, 235, 28, 249, 31, 23, 152, 225, 157, 37, 221, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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