Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 238cb8d419ec6504788a813c063fcc6231f91bd5869d0ca1daede0a71f8c52b4

Tx prefix hash: 2b39721c8b5075fa03cbb66a440118824a255775978d868b9e429fa5fdeacf40
Tx public key: 93522a4bb768de9fa1336d734c316cd5d7ef213657043fd8fda281f662f4c4c4
Timestamp: 1724648367 Timestamp [UCT]: 2024-08-26 04:59:27 Age [y:d:h:m:s]: 01:074:13:11:22
Block: 1096086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311736 RingCT/type: yes/0
Extra: 0193522a4bb768de9fa1336d734c316cd5d7ef213657043fd8fda281f662f4c4c4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c39a8be96a387f35ae94e0f8afcbc5533c48f1857681fab47953cd7f4c4602e 0.600000000000 1571273 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": 1096096, "vin": [ { "gen": { "height": 1096086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c39a8be96a387f35ae94e0f8afcbc5533c48f1857681fab47953cd7f4c4602e" } } ], "extra": [ 1, 147, 82, 42, 75, 183, 104, 222, 159, 161, 51, 109, 115, 76, 49, 108, 213, 215, 239, 33, 54, 87, 4, 63, 216, 253, 162, 129, 246, 98, 244, 196, 196, 2, 17, 0, 0, 0, 2, 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