Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ac029c9f21abba5c3b4b2c33201b84bdd2179733538d060418d87d32770c76a

Tx prefix hash: 5ebd62b70999871ab389a0d2b81e1143c383d31e6f2e93fe60713510b18827d0
Tx public key: 1f00e8b69b1b1db094e4f96c142721bcd147ecb838481ffe7a3e831da99ce17b
Timestamp: 1724181327 Timestamp [UCT]: 2024-08-20 19:15:27 Age [y:d:h:m:s]: 00:226:00:59:51
Block: 1092231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161400 RingCT/type: yes/0
Extra: 011f00e8b69b1b1db094e4f96c142721bcd147ecb838481ffe7a3e831da99ce17b021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eda7e62aecce7f86185befa407a7a15efc0b3dc99c6eedebd3ca1ad7421cdf4 0.600000000000 1566936 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": 1092241, "vin": [ { "gen": { "height": 1092231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eda7e62aecce7f86185befa407a7a15efc0b3dc99c6eedebd3ca1ad7421cdf4" } } ], "extra": [ 1, 31, 0, 232, 182, 155, 27, 29, 176, 148, 228, 249, 108, 20, 39, 33, 188, 209, 71, 236, 184, 56, 72, 31, 254, 122, 62, 131, 29, 169, 156, 225, 123, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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