Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a42174f08c7eccf9fddc2e745b4cb22491549f8acc6e3087150b76bfe2c03292

Tx prefix hash: 699b90371bd12f3b1d93316047e33dcfa77e2d2679ecda54ec82d4c516d4c7be
Tx public key: 432cf581565a262bf36ae85927079352db35bfae5f8b2488bf3063c1b267cde3
Timestamp: 1725530053 Timestamp [UCT]: 2024-09-05 09:54:13 Age [y:d:h:m:s]: 01:063:12:31:32
Block: 1103406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303831 RingCT/type: yes/0
Extra: 01432cf581565a262bf36ae85927079352db35bfae5f8b2488bf3063c1b267cde302110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dc53b82bf7386f67d658883109adfb540fd26e0517242d383c65ed6ef1d5c5e 0.600000000000 1580223 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": 1103416, "vin": [ { "gen": { "height": 1103406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dc53b82bf7386f67d658883109adfb540fd26e0517242d383c65ed6ef1d5c5e" } } ], "extra": [ 1, 67, 44, 245, 129, 86, 90, 38, 43, 243, 106, 232, 89, 39, 7, 147, 82, 219, 53, 191, 174, 95, 139, 36, 136, 191, 48, 99, 193, 178, 103, 205, 227, 2, 17, 0, 0, 0, 12, 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